-
Note: the issue was created automatically with bugzilla2github tool
Original bug ID: BZ#5406
From: @ggonthier
Reported version: 8.6
CC: @ejgallego, @herbelin
-
Right now we simply fail if you try and pass a return value of one type as an argument to another function, but we should probably understand that some types of casts (like `bytes` to `string` and `by…
-
`mapMonotonic coerce = coerce` and `mapKeysMonotonic coerce = coerce`, or so.
-
If we have a structure `S := {T of m T}` composed of one mixin `m`, there is a coercion from `S` to `m` (which is currently available and reliable upon).
Now if mixin is turned into a factory which…
-
When defining a route with an array value in the query params like so:
```
{:get {:parameters {:query {:strings [string?]}}
:handler (fn [{{:keys [query]} :parameters}]
…
-
The following are semantically equivalent:
```zig
const a = T{};
const a: T = .{};
const a = @as(T, .{});
```
I propose to remove the first possibility, and rely on the other two.
The pro…
-
The GraphQL gem leaves a lot to be desired when it comes to type coercion, and likely for good reason. We can likely tie into the middleware: https://rmosolgo.github.io/graphql-ruby/schema/configurati…
-
We currently use type class resolution to implement coercion resolution.
The type classes are defined in the following file
https://github.com/leanprover/lean/blob/master/library/init/coe.lean
The …
-
In Kotlin we have specific highlighting for smart casts and a tooltips about it
![image](https://user-images.githubusercontent.com/3221931/31169995-29d41ee4-a903-11e7-8e0e-203b01d6ef53.png)
I want…
-
The Coercion functions for Scalars are currently named:
1. serialize: this is result or output coercion
2. parseValue: this is runtime object input coercion
3. parseLiteral: this is Ast litera…