Dan0042 (Daniel DeLorme)

  • Registered on: 06/09/2016
  • Last connection: 11/20/2019




02:52 PM Ruby master Feature #16345: Don't emit deprecation warnings by default.
Personally I'd like to have this feature as an attribute accessor of `Warning`. So it's easier to set the value based... Dan0042 (Daniel DeLorme)


06:43 PM Ruby master Feature #16131: Remove $SAFE, taint and trust
Wait, I don't understand. You should be able to just leave `str.untaint` like it is since it's just a no-op in 2.7. W... Dan0042 (Daniel DeLorme)


01:50 PM Ruby master Feature #14183: "Real" keyword argument
> As it stands the deprecation warning writes to STDERR every time it hits a bad usage. Running our spec suite causes... Dan0042 (Daniel DeLorme)


04:09 PM Ruby master Feature #16295: Chainable aliases for String#-@ and String#+@
It would be nice to see some real-world examples where chaining of these methods makes sense. `"foo".-.size` (always ... Dan0042 (Daniel DeLorme)
02:43 PM Ruby master Feature #16276: For consideration: "private do...end" / "protected do...end"
> - Possibility #3: renders SyntaxError. This requires a massive rewrite of our parser. Theoretically possible but ... Dan0042 (Daniel DeLorme)


04:53 PM Ruby master Feature #16296 (Open): Alternative behavior for `...` in method body if `...` is not in method definition
In #16253 we settled on a syntax where the remainder arguments captured via `...` in the method definition can be for... Dan0042 (Daniel DeLorme)


04:41 PM Ruby master Feature #16289: Reduce duplicated warnings for the change of Ruby 3 keyword arguments
> > If they only warn once, they are not that annoying, and people may be less inclined to fix the issue.
> It's...
Dan0042 (Daniel DeLorme)
04:17 PM Ruby master Feature #16153: eventually_frozen flag to gradually phase-in frozen strings
Eregon (Benoit Daloze) wrote:
> For this discussion, I would focus on having this for Strings only initially.
Dan0042 (Daniel DeLorme)
03:22 PM Ruby master Feature #11660: a falsy value (similar to js undefined) that facilitates forwarding of default arguments
alanwu (Alan Wu) wrote:
> Since the beginning of time (correct me if I'm wrong), the two falsy values in Ruby has be...
Dan0042 (Daniel DeLorme)
01:51 PM Ruby master Feature #13083: Regexp#{match,match?} with a nil argument are deprecated and will raise a TypeError in Ruby 3.0
Is there a benefit to the change apart from consistency? A concrete benefit I mean. Dan0042 (Daniel DeLorme)

Also available in: Atom