-
#18 added a schema for the Typst builtin type "stroke". But most of the time `stroke` arguments accept either one of `stroke`, `length`, `color` or `dict`. Similarly `fill` usually accepts `color`, `g…
jneug updated
3 months ago
-
path = system.file("extdata", "example.txt", package = "PreMSIm", mustWork = TRUE)
input_data = data_pre(path, type = "ID")
msi_pre(input_data)
> path = system.file("extdata", "example.txt", packag…
-
### Zig Version
0.14.0-dev.367+a57479afc
### Steps to Reproduce and Observed Behavior
Attempt to compile the following code:
```zig
pub fn main() void {
const n: u8 align(2) = 42;
…
-
-
It looks like method lookup thinks that we do automatic coercion
```
import java.lang.Math
def main(): Float32 \ IO = Math.max(32f32, 0)
```
```
Verifier error:
Mismatched types near ..\test.fl…
-
`prefer-native-coercion-functions` is used to simplify methods like `filter` that are simply trying to find truthy values. However the native type castings do not provide any typescript assertions, so…
-
We have this doctest example:
```python
x = Quantity([1, 2, 3], "Kelvin")
with u.add_enabled_equivalencies(u.temperature()):
y = x.to(u.deg_C)
```
which works, but this one doesn't work:
```python…
-
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…
-
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…
-
When passing properties to a component, would you prefer that the properties are type checked and throw an exception in case of wrong type, or rather allow JavaScript to implicitly type coerce, i.e., …