The handling of timeouts is [documented][1], but that only shows it with a `handle_interrupt` block set up around everything, not under `ensure`. In the examples shown here, can `ensure;begin` or `ensure;Thread.handle_interrupt` be consi...avit (Andrew Vit)
For symmetry, we also have `<<-` for heredocs "take this input for..." It might make sense to think of `->>` as "give this output to..."avit (Andrew Vit)
matz (Yukihiro Matsumoto) wrote: > If you really wanted a non-unwrapping method for promises, use `yield_self`. If I understand what you mean by "unwrapping" here, the new method still doesn't `call` yielded procs to make them compos...avit (Andrew Vit)
Is there a valid reason for this behaviour? It looks like a bug to me: ~~~ require 'cgi' params = CGI.parse("") params["x"] #=> [] ~~~ (Expected nil) I looked at history and it looks like it has been there from the very b...avit (Andrew Vit)
If adding keyword options, would it make sense to add the possibility to enumerate by `>>` for whole months instead of only `succ` days, or is that out of scope here?avit (Andrew Vit)
Some elements of ruby style are hard to check statically because they encode semantics. For example, I prefer to write blocks using [Weirich Braces][1]: this feels less arbitrary than changing syntax for single vs. multi-line blocks. ...avit (Andrew Vit)
An alternate (short but cryptic) way: ``` str = "one\ntwo" str.gsub(/^.*/m, '<\0>') ``` - gsub! can do it destructively - using `/m` can control if it wraps each line, or all (A similar usage for wrapping characters in a str...avit (Andrew Vit)
My only point was that symbols are not meant to be operated on the same as strings, because they do serve different purposes. They can serve as a kind of lightweight type-safety when you are dealing with an internal identifier, but in pr...avit (Andrew Vit)