bughit (bug hit)
- Login: bughit
- Registered on: 10/29/2014
- Last connection: 06/22/2021
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 0 | 0 | 0 |
| Reported issues | 10 | 24 | 34 |
Activity
07/20/2021
-
08:27 AM Ruby master Feature #18040: Why should `foo(1 if true)` be an error?
- > implicit casting from a statement to an expression within a method definition body
It's not just the method body...
07/19/2021
-
- jeremyevans0 (Jeremy Evans) wrote in #note-4:
> You may want to read the definition of `stmt` in parse.y, particularl... -
- ```rb
def foo
2
1 if false
end
p foo
```
foo returns nil, the value of the last expression `1 if false... -
- jeremyevans0 (Jeremy Evans) wrote in #note-1:
> `1 if true` is a statement and not an expression
`1 if true` is a... -
- There's no ambiguity here that should require another set of parens `foo((1 if true))`
03/12/2021
-
- since procs and lambdas are of the same type, as long as Proc::new exists, it should be able to create either.
```...
08/11/2020
-
- > another reason is avoidance of alias effects
What you've shown is not another reason for freezing.
`a = b = "...
08/10/2020
-
- > However in my view what defines a literal, is the use of a specific syntax, so ""
There is only one reason for f...
08/05/2020
-
- Can't we just treat this as I feature request? The reasons are, it will reduce allocations, be more logical, less sur...
-
- If you want to get a mutable string from an interpolated literal `+"_#{method1}_"`, 2 allocation will be done instead...
Also available in: Atom