repl_type_completor 0.1.18 handles the error recovery node that prism now wraps invalid write targets in, so its test failures no longer need to be ignored. This reverts commits 2979ed4723, 1e71e987c2 and 5cefc5f906. Co-authored-by: Cl...tompng (tomoya ishida)
partial_value rebuilds the open containers on a scratch copy of the value stack. Folding an empty innermost container pops nothing and pushes its result, so head climbs one past the live size; the scratch buffer was sized to exactly the ...tompng (tomoya ishida)
Proc's source in the code below consists of 3 parts. `do`, `inside\n<<B; end`, and `exclave\nB`. ```ruby <<A; tap do outside injected A inside <<B; end; outside exclave B ``` Even if heredocs are used, I think `do` is the s...tompng (tomoya ishida)
Shorter reproduction code: ~~~ruby require 'bigdecimal' 4.times.map do Ractor.new do loop { raise unless BigDecimal(3.14) } end end sleep 1 GC.start ~~~ I guess this is a bug of BigDecimal's float parsing logic. If the...tompng (tomoya ishida)
I think checking code validness is hard for the code below. Warning check is triggered at every line, each check needs to parse till the bottom. ~~~ruby a -1 => b # only a(-1 => b) is valid, (a - 1) => b is invalid at the `2 => 3` pos...tompng (tomoya ishida)
The same thing can be also said to `a=[1,2]` and `a=1,2`. In Prism, these are both parsed as ArrayNode with/without opening and closing. In AbstractSyntaxTree, the non-abstract parts (bracket) are dropped. I think it's just a restricti...tompng (tomoya ishida)
`return a, &b` is syntax error in parse.y, but accepted in Prism ~~~ruby Prism.parse_success?('return a, &b') #=> true RubyVM::AbstractSyntaxTree.parse('return a, &b') #=> block argument should not be given (SyntaxError) ~~~ W...tompng (tomoya ishida)