-
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…
-
Javascript does not have distinct integer and float types. Therefore, 2.0 and 2 are equal.
When 2.0 is sent to the server (at least in JSON; probably also in Transit, though I've not tested), the s…
-
Hi, thanks for writing this library! I like the cleanliness of the code and it appears to be wicked fast 🔥
Have you thought about adding type coercion? It's the only thing keeping me from switchin…
-
This seems like it should work: [Playground link](https://is.gd/Q8MWVS)
```rust
use std::sync::Arc;
trait Foo {}
struct Bar;
impl Foo for Bar {}
fn takes_foo(foo: &Foo) {}
fn main()…
-
There's already a [Types::UUID](https://metacpan.org/pod/Types::UUID) type, but it builds on UUID::Tiny, while Attean uses the more advanced Data::UUID, and I suppose it might not be a good thing to c…
-
More of a question/potential enhancement request than anything. Basically, I was just wondering what it would take to create methods to coerce existing objects into a DataFrame object? I would imagi…
-
[This (playground):](https://play.rust-lang.org/?gist=c95124c2c3f228927fb6632c7f6e1137&version=stable&mode=debug&edition=2015)
```rust
fn foo() {}
fn bar() {}
fn main() {
let _ = [(foo), (b…
-
I'm beginning to suspect that having multiple coercion paths between two classes is a bad idea, for making proofs easily. Does anyone else think so?
Here is what's bugging me today:
```
…
-
Is there any plan for adding field coercion along the validations?
-
Note: the issue was created automatically with bugzilla2github tool
Original bug ID: BZ#2372
From: @amahboubi
Reported version: 8.3
CC: @herbelin