FLIP 210: propose an improvement to entitlement mapping syntax

[dsainati1]

Some feedback in Discord (https://discord.com/channels/613813861610684416/1159198731422412821) revealed some room for improvement in the visual clarity of entitlement mapping declarations. This proposes to make them more visually distinct.

[jacob-tucker]

I am a big fan of this because of the reasoning specified:

since one of them has default behavior for public access and the other prevents it

So this is a +1 from me.

If before Cadence 1.0 is released and there are further changes to default public access on behalf of mappings or regular entitlements, then we should revisit this again.

[turbolent]

👍

Even though this makes programs a bit more verbose, this is a big improvement for readability.

Especially when a entitlement or entitlement mapping is imported, reading a declaration currently requires looking up the imported declaration to see what access will be granted when accessing the member.

[bjartek]

+1

At this point cadence is verbose, and this makes it easier to reason about.

[bluesign]

+1

[SupunS]

👍

[dsainati1]

We discussed this in the language design meeting today and the FLIP is approved.