| Age | Commit message (Collapse) | Author |
|---|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6890
|
|
Pick from https://github.com/ruby/syntax_suggest/commit/daee74dcb06296fa69fe8595fdff5d93d432b30d
Notes:
Merged: https://github.com/ruby/ruby/pull/6890
|
|
|
|
```
$ ruby tool/sync_default_gems.rb syntax_suggest
Sync ruby/syntax_suggest
```
https://github.com/ruby/syntax_suggest/pull/161
Notes:
Merged: https://github.com/ruby/ruby/pull/6831
|
|
Due to a problem with ripper we do not recognize `break` as invalid code. It's confusing that "Syntax OK" is output in that case.
When there's no syntax error, the algorithm should not say anything. The exception is in the CLI and that's for compatibility with `ruby -wc`
```
$ cat /tmp/break.rb
break
⛄️ 3.1.2 🚀 /Users/rschneeman/Documents/projects/syntax_suggest (schneems/no-syntax-not-okay-break)
$ ruby -wc /tmp/break.rb
Syntax OK
```
> Note that this is invalid, running this code will raise a Syntax error.
```
$ exe/syntax_suggest /tmp/break.rb
Syntax OK
```
Close https://github.com/ruby/syntax_suggest/pull/157
https://github.com/ruby/syntax_suggest/commit/d7bd8f03a2
|
|
https://github.com/ruby/syntax_suggest/commit/14e8cdc916
Notes:
Merged: https://github.com/ruby/ruby/pull/6824
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6287
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6287
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6287
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6287
|
