-
Existing type coercion behavior is implemented pretty well in the environment variable handling logic, given that all environment variable values are strings on input. But sourcing parameters from els…
-
### Summary
We are proposing to clearly define the options when creating a schema, for example the backend. Additionally we are proposing to remove the Optional flag as it is documented as a direc…
-
AFAF: https://try.haxe.org/#52ff1319
```haxe
@:using(Test.MyEnumUtils)
enum A {
VA;
VB(isX:Bool);
}
abstract B(A) from A {
@:to function toString() return this.toString();
}
…
-
I think `DISALLOW_TYPE_COERCION` and `ALLOW_TYPE_COERCION` are not using the correct values. [Here](https://github.com/OpenDDS/OpenDDS/blob/master/dds/DdsDcpsCore.idl#L298) `DISALLOW_TYPE_COERCION` is…
-
Related to https://github.com/opengeospatial/ogc-geosparql/issues/398, https://github.com/opengeospatial/ogc-geosparql/issues/542
At the last meeting we discussed distortions caused by coercing to …
-
Currently there is no way to tell Zod "if you get a single value of correct type, just put it into an array". Existing `.coerce()` operation could be used for this.
Here is a reference implementati…
-
Consider [this example](https://play.rust-lang.org/?version=nightly&mode=release&edition=2021&gist=a5400c33cb7e257b0d795cbdb4b7a389):
```rust
pub fn testcase() -> *const dyn Bar {
let baz: &dyn…
-
Currently, `Vector` has the inferred role `type role Vector representational phantom nominal`, which allows the following:
```haskell
newtype Foo = Foo (Vector 10 Int)
exVec :: Vector 15 Int
exV…
-
### What is the problem this feature would solve?
I'm using Kubb for a serverless API, and i use to to generate Zod-schemas from my OpenApiSpec.
In this case I'm making use of the `coerce` feat…
-
> One other nit: https://docs.siv.org/compare conflates coercion resistance and vote selling. These are actually two different things, and have different definitions in the literature (see the Bernhar…