Explore >> Select a destination
|
You are here 
|
mislav.net | ||
| | | | |
thomascountz.com
|
|
| | | | | tl;dr Numbered block params (_1, _2, etc.) are reserved and read-only, while it (the new block param in Ruby 3.4) has different mutation rules for compatibility. Using combined assignment operators (e.g. +=, &&=), numbered block params could be overwritten without error due to a discrepancy between parse.y and Prism (Ruby's default parser since 3.3). A patch has been applied to Prism in Ruby 3.4.2 to explicitly check for writes to numbered params via combined assignment operators. The Bug In Ruby, block-local numbered parameters (_1, _2, etc.) provide a concise way to reference block arguments without explicit naming. They have received renewed attention recently with the introduction of the it parameter in Ruby 3.4. Though they serve a similar purpose, numb... | |
| | | | |
citizen428.net
|
|
| | | | | As promised in my previous post this article will cover some of the more advanced features of Crystal, namely macros, C bindings and concurrency. Macros When coming to Crystal from Ruby, one of the biggest changes is the lack of runtime introspection that enables much of Rubys metaprogramming techniques. However, this can be rectified to a certain degree by using macros, which are methods that receive AST nodes at compile time which they use to write new code. | |
| | | | |
zverok.space
|
|
| | | | | ||
| | | | |
www.jhmcstanton.com
|
|
| | | [AI summary] The author reminds readers about the ongoing Advent of Code 2019 programming challenge, which releases two daily problems from December 1st to 25th, and mentions their personal progress and encouragement for others to participate. | ||
