Johannes Müller

> I do have other crystal projects on the same machine that do not exhibit this behavior. That's really odd. There is something shady going on and I would expect...

Okay, actually running the method with `Dir.children` makes a little more sense now. Only just a little, though. It seems there's indeed some remnant of the process lingering around even...

Not sure if it's related but I encountered a bunch of similar errors in this CI job: https://github.com/crystal-lang/crystal/actions/runs/19103122801/job/54579813469 The errors are coming from the linker, not Crystal itself. ``` 2)...

Summary from private conversation: Adding bounds checking to `Pointer::Appender` could be a simple solution at least for `push` semantics. However, I associate `Pointer` with unbounded access, so it feels a...

What's the motivation for `Tuple` in the first place? I frankly don't really see many use cases for this. The example `KEYWORDS = %t[foo bar baz]` does not look like...

Reduced reproduction: ```cr def foo(arg : Int32 | String | Nil) # or foo(arg) end def foo(arg : Int32) end def foo(arg : Int32 | String) end foo(nil.as(Int32 | String...

I'm not convinced that the proposed fix is correct. There is some other component at play: reproducing this issue requires a catch-all overload. When the first def has the signature...

I find this language feature is quite a quirky oddity. If we could start over, I'd strongly argue to leave it out of the language. It leads to many surprises....

This specification seems actually incorrect: `next` is allowed inside a captured block. ```cr def capture(&block : -> Int32) block end capture do next 1 end.call # => 1 ``` The...

> Maybe add a note or something to explain why we eventually override the token's delimiter state? I figured this should be rather obvious from the use of the `previous_delimiter_state`...