Skip to content

Warn on modified future frozen string literal - #549

Closed
etiennebarrie wants to merge 11 commits into
masterfrom
warn-on-modified-future-frozen-string-literal
Closed

Warn on modified future frozen string literal#549
etiennebarrie wants to merge 11 commits into
masterfrom
warn-on-modified-future-frozen-string-literal

Conversation

@etiennebarrie

Copy link
Copy Markdown
Member

No description provided.

@rubyFeedback

Copy link
Copy Markdown

With byroot suggesting it on the ruby tracker not too long ago, will it be proposed for an upcoming ruby developer meeting as well?

@etiennebarrie
etiennebarrie force-pushed the warn-on-modified-future-frozen-string-literal branch 2 times, most recently from 0b5cb1f to 0b61e41 Compare March 11, 2024 09:44
@casperisfine

Copy link
Copy Markdown

repro:

o = "test"
def o.test
end
o.test

@casperisfine

Copy link
Copy Markdown

We'll need ruby/prism#2577 to be fully green.

@casperisfine
casperisfine force-pushed the warn-on-modified-future-frozen-string-literal branch 2 times, most recently from db34647 to b41de40 Compare March 14, 2024 14:42
@casperisfine

Copy link
Copy Markdown

Alright, we're now at the stage where we're failing on make test-spec, which is being handled in ruby/spec#1142

@casperisfine
casperisfine force-pushed the warn-on-modified-future-frozen-string-literal branch 3 times, most recently from 628b631 to 4424995 Compare March 14, 2024 21:47
@casperisfine
casperisfine force-pushed the warn-on-modified-future-frozen-string-literal branch from 44fe2c1 to ab2f29b Compare March 15, 2024 08:54
@casperisfine

Copy link
Copy Markdown

Moving to ruby#10262

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants