Hanami
I鈥檓 at RubyConf!
Lifelong learner. I鈥檓 building a Ruby, called Natalie, for fun. I sometimes record hacking sessions on YT.
| Videos | https://youtube.com/TimMorgan |
| Website | https://timmorgan.dev |
| GitHub | https://github.com/seven1m |
Tim Morgan
- 177 Followers
- 71 Following
- 38 Posts
First merged PR from the #RubyConf24 hack day, thank you @seven1m!
Don't allow creating a new app with certain confusing names by seven1m 路 Pull Request #272 路 hanami/cli
I'm at RubyConf! Thanks for letting me sit at the hack day table and talk about Hanami a bit. If this is the wrong direction, feel free to pick it apart or summarily close if not exactly what y...
I was at RubyConf yesterday too. But I was antisocial yesterday lol.
Totally forgot about this place. I鈥檓 doing nothing cool right now, so probably just as well!
I really just wanted to know if Thread#alive? returns true during this special "aborting" state. It does!
Ruby threads have a special "aborting" status that's really hard to observe. The more you know!
(I recycled this thread from a recent PR description, in case you are interested! https://github.com/natalie-lang/natalie/pull/1650)
This is in contrast to Thread.report_on_exception and Thread#report_on_exception, which seem to behave like a "default" and a "local" as I would expect. Changing Thread.report_on_exception affects any threads created after that, and you can override the setting with Thread#report_on_exception.
Weirdly inconsistent!
There is scarce documentation about this, but my observation is that Thread.abort_on_exception is not a "default" setting for new threads, but rather a sort of "global" setting. If either the global or the local setting is true, then the thread causes the main thread to abort when there is an unhandled exception.
...at least, that's how it appears to work. 馃槄