Ary Borenszweig comments

Results 414 comments of


                                            Ary Borenszweig

Allow array destructuring to produce nil values

Maybe I didn't make myself clear, but the idea is not to change how `days, hours, minutes = time_components` work but, as I proposed in #2617 to be able to...

Allow array destructuring to produce nil values

To be honest, I don't think we'll do anything about this. You get an index error whole changing code and that's totally fine.

Instance variable '@callback' of Foo must be (Proc((T | Nil)) | Nil), not Proc(Nil)

Right now, a proc that returns X isn't implicitly castable to a proc that returns X | Y. In your case you have `->{}`, which is `Proc(Nil)`, but you require...

Instance variable '@callback' of Foo must be (Proc((T | Nil)) | Nil), not Proc(Nil)

The problem is that a proc doesn't know what type it returns, only the compiler knows this when generating the executable. So, if you have a Proc returning X, when...

Instance variable '@callback' of Foo must be (Proc((T | Nil)) | Nil), not Proc(Nil)

as doesn't work, I was just saying there's a way to fake it. And no, these casts will never be done

Crystal::System::Process#spawn forks, should call posix_spawn() or posix_spawnp() instead

Oooh...! `fork` doesn't work at all in interpreted mode, but I don't know why. Maybe we could at least avoid it in that scenario?

`nargo fmt` panicked

This was fixed in the past when we started parsing `if` as a statement, in addition to parsing it as an expression.

throw and catch with `SkipMacroException`

> Yet we make use of this concept in the compiler I don't quite agree. We use exceptions for control flow. That's contrived, but valid. People do this in languages...

throw and catch with `SkipMacroException`

Yet another alternative is to deprecate skip_file and stop using it. You can achieve the same thing by not requiring a file.

throw and catch with `SkipMacroException`

I also wonder whether anyone outside this repo is using skip_file. My guess is no, because we use it for platform-de pendent code. In that case, we could refactor our...