[Bug]: Model properties called const without backticks no longer valid - undocumented breaking change in 0.57

[adamscybot]

Describe the bug

Since 0.57 a model with a property (incidentally) called const no longer compiles unless it is wrapped in backticks.

In 0.56 this was allowed. In 0.57, presumably the change has come about because of the new const language functionality.

I have assumed here that this is therefore an intentional behavioural change, so have concluded it's just missing from the release notes 🙂. This had me confused for a little while.

But also probably need someone to chime in in case this wasn't actually expected.

Reproduction

• ✅ 0.56 - const model property - no quotes
• ❌ 0.57 - const model property - no quotes
• ✅ 0.57 - const model property - with backticks

As you can see between first two repro's theres a potential breaking change here.

Checklist

• Follow our Code of Conduct
• Check that there isn't already an issue that request the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion.
• The provided reproduction is a minimal reproducible example of the bug.

[timotheeguerin]

Hhm this is a good point I’ll add that in the release notes, we are planning to relax use of keyword in some context like model property to both reduce those breaking changes in the future as well as be less confusing for new users.

[bterlson]

Yeah we really gotta allow keywords as member names.