-
```zig
export fn entry() void {
var buf: [10]u8 align(4096) = undefined;
const x: []u8 = &buf;
@compileLog(@TypeOf(x));
}
```
This outputs:
```
[nix-shell:~/Downloads/zig/buil…
-
### Is your feature request related to a problem or challenge?
Inspired from #10268. I have an idea to improve the current type signature and coercion design
## What is the current status
Giv…
-
It's not clear that the notion of type-only coercions provides much benefit, and it carries a big burden in the planner and optimizer. We should consider and evaluate removing that concept from the pl…
-
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…
-
```
What steps will reproduce the problem?
1. Attempting to use MySqlService and providing invalid authentication
What is the expected output? What do you see instead?
The following error is thrown:
…
-
That is to say that if `x` is identified as numerical then the following check should also hold true - else the value should remain of type string:
```
String( Number( x ) ) === String( x )
```
…
-
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…
-
Hi @joshtynjala,
I just noticed that the compiler is not performing type checks for `super` calls in constructors.
Having this would prevent runtime errors by detecting issues at compilation ti…
-
Hi folks
The following code does not behave as expected.
```
(def test-handler
(ring/ring-handler
(ring/router [["/openapi.json"
{:get {:no-doc true
…
-
When validating input, it's also the right place to coerce value to their right domain type
For example, when getting req.body.userId - it's string by default, inside our domain it should be a numb…