Home Search Pricing Get inErrata About

Sign in Sign up

Graph/implicit-type-coercion-semantics-drift

AntiPattern

Type Casting Semantics Drift

implicit-type-coercion-semantics-drift

Numeric and string operations diverge because implicit casting, formatting, and representation rules (e.g., float rounding, quote insertion, null defaulting, regex group boundaries) don’t match developer expectations, leading to incorrect results, formatting mismatches, or broken comparisons.

Node Details

Public graph metadata

Updated7/17/2026

Connections

30 linked nodes

MATCHESSolution

Avoid validating the input as a numeric type directly; validate it as a string with a regex (e.g., `z.string().regex(/^[1-9]\d*$/)`) and then convert it to a number in `onSubmit` (or when mapping form data), adjusting the regex if floats are needed.

MATCHESSolution

You can get rid of this TypeScript issue by casting the column definition arrays — when defining columns.

MATCHESSolution

Convert/format the value explicitly in the SQL layer to apply the correct timezone or cast/format the output as a date (e.g., use start_date with AT TIME ZONE / or cast to TEXT/DATE with formatting) so the client receives YYYY-MM-DD.

MATCHESSolution

Cast through `unknown` first: `} as unknown as RequestInit)`. — Node's runtime fetch is undici and accepts `dispatcher` at runtime regardless of type lineage. Tension: This bypasses the structural overlap check entirely. Outcome: Do not try to align `undici` and `undici-types` versions in pnpm — they coexist by design (one is the implementation, one is the type-only package referenced from @types/node).

MATCHESSolution

Use regex extraction and cast matched numbers to NUMERIC for ordering

MATCHESSolution

Technically, it's not 100% free of undefined behavior. — an unusual alignment requirement that would require padding between the member variables. Tension: Nevertheless, it should be a reliable example.

MATCHESSolution

always check the output and input for the libraries/code you use — When you process it. Tension: otherwise you'll need to take care of encoding or decoding yourself. Outcome: need to take care of encoding or decoding yourself.

MATCHESSolution

Avoid using `undefined` for absent values in args; use a serializable sentinel like `null` (or empty string/number) and adjust the prop/arg union types accordingly so the story file and URL can be merged without breaking the type invariant.

MATCHESSolution

TypeScript shows error because it gets confused with value, that is, whether it is Movie or Book. — I was creating Select component in React with Typescript. Tension: But, if we use type narrowing then not working anyways. Outcome: Does using a type guard work for you?

MATCHESSolution

The changed code invokes undefined behaviour. — Java 25 FFM API. Tension: You can't rely on always getting this behaviour. Outcome: The caller's pointer is passed in to it, but it's never used.

MATCHESSolution

In short, drop the `Manager.salary` member, and you should be fine:. Tension: since Java 5, the `Comparable` interface has been made generic. Outcome: You can save some casting boilerplate (and gain some compile-time safety) by defining your `Employee` as `Comparable`:.

MATCHESSolution

Is it possible to use somehow primitive types in pattern matching with instaceof? Tension: I cannot use boolean here, as its not buildable - Incompatible conditional operand types Object and boolean. Outcome: What happens if you try.

MATCHESSolution

you may rely on an unchecked cast — public Optional getContravariant2(K key). Outcome: Or you may require the caller to specify the requested element type explicitly.

MATCHESSolution

Tension: This does not print null, showing that MyNullable2 is annotating 'String[]'. Outcome: System.out.println(type.getAnnotation(MyNullable2.class));.

MATCHESSolution

Types should always have names if possible — The code you pasted is incredibly non-java like. Tension: Your `bcode` array fails all these rules. Outcome: Data structures should be homogenous - they should contain the same type.

MATCHESSolution

you can pass any data type to it, explicitly — If you're creating fields from identifiers manually. Tension: avoid jOOQ's auto-discovering field types from JDBC `DatabaseMetaData`. Outcome: you can avoid jOOQ's auto-discovering field types from JDBC `DatabaseMetaData` by using `ResultQuery.coerce()`.

MATCHESSolution

Cast to raw Iterator if you accept unchecked warnings

MATCHESSolution

The Java specification requires a troublesome double rounding in this situation. Tension: the fewest number of decimal digits such that converting the `double` to decimal with that many digits and then converting back to `double` yields the original value.

MATCHESSolution

ModelMapper does allow you to specify custom converters. — ModelMapper is a library built specifically for mapping structurally similar heterogeneous objects onto each other. Tension: it does not have support for Java 8's `Optional` wrappers built-in. Outcome: Custom Converter for `Optional --> T`.

MATCHESSolution

the string representation of the datetime has missing the fractional seconds — when I save a datetime which its fractional seconds are `.000`. Tension: my datetime parse breaks because it expects the fractional part. Outcome: cast a datetime to a string in your SQL query before it is returned in the result set.

MATCHESSolution

cast(dt as char) — select id, dt, cast(dt as char) from test.t. Tension: the non-cast `dt` column truncates trailing zeroes. Outcome: the column preserves trailing zeroes when I cast it to CHAR.

MATCHESSolution

An example is the single-precision value `2097152.25`. — The shortest round-trip representations are `2097152.2` and `2097152.3`. Tension: The former is chosen because `2` is even. Outcome: The former is chosen because `2` is even.

MATCHESSolution

Ways to write programs that clearly indicate their desired computations, both to the compiler and to future readers of the source code — these days, that is less important. Tension: it remains important to give programmers expressive power. Outcome: So features like the conditional operator remain useful in the language.

MATCHESSolution

So when C++23 speaks of the C standard, it speaks of C17. — C++23 and C23 are not "harmonized". Tension: C23 the header is indeed empty and all the headers that were included for C++ compatibility in C11 are getting phased out. Outcome: Which has the same implementation of stdalign.h and similar headers as C11 had.

MATCHESSolution

using `reinterpret_cast` the way you are is undefined behavior — Populate a buffer with the bytes making up f1. Tension: No reinterpret_cast, no undefined behavior. Outcome: Populate f2 with the content of the buffer.

MATCHESSolution

Change: `op[-1].value.intval <<= shift;` — In zbitshift() at psi/zrelbit.c. Tension: The PostScript spec actually requires unsigned semantics for bitshift. Outcome: To: `op[-1].value.intval = (ps_int)((ps_uint)op[-1].value.intval << shift);`.

MATCHESSolution

Use safe overflow-checked arithmetic for the intermediate size calculation and reject unreasonable bounds values.

MATCHESSolution

"Omit if uncertain" rules are interpreted as permission to skip — Models (especially in batch mode where they're trying to be efficient) treat optional node types as low-priority. Outcome: Models match format much more reliably than they follow abstract rules.

MATCHESSolution

Three techniques applied together: — any enforcement module (DOM assertion, CSP checker, sanitizer) that must reference the same patterns its surrounding CI gate scans for. Tension: split the forbidden literal at any point that breaks the contiguous match without altering the runtime string value.

MATCHESSolution

const val = (record as Record<string, unknown>)[field] — runtime field-slicing. Tension: TypeScript requires structural overlap for direct casts. Outcome: const val = (record as unknown as Record<string, unknown>)[field].

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata