mlarraz (Matt Larraz)
- Login: mlarraz
- Registered on: 12/01/2015
- Last sign in: 01/05/2016
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 0 | 0 | 0 |
| Reported issues | 0 | 2 | 2 |
Activity
01/23/2016
-
06:27 AM Ruby Bug #12015 (Closed): Improving code coverage visibility
- In https://bugs.ruby-lang.org/issues/10189 the simplecov gem was added to generate coverage reports for specs.
However, the docs in `coverage/README` are very sparse and appear to be out of date. At least, I haven't been able to gener...
01/03/2016
-
07:04 AM Ruby Feature #11911: Immutable method definitions and/or static dispatch
- I suppose I'm talking specifically about the first, that is, the ability to change any method at any time.
The most obvious use case I can imagine is an application that wants to guarantee that it's running the stock stdlib, with no m...
12/28/2015
-
06:17 PM Ruby Feature #11911 (Feedback): Immutable method definitions and/or static dispatch
- One of Ruby's biggest strengths is the ability for anyone, at any time, to redefine (almost) any behavior. But this is also one of its biggest weaknesses.
Ruby has a very liberal dynamic dispatch, so any method can be redefined anywhere...
12/16/2015
-
12:38 AM Ruby Feature #11816: Partial safe navigation operator
- My naïve understanding is that `foo&.bar` should be a shorthand for `foo && foo.bar`, and therefore the `&.` operator should take the same level of precedence as the `&&` operator.
Marc-Andre Lafortune wrote:
> ```ruby
> ...
If you ...