Annoying warnings about stuff which is not used

[Sandy]

There are many cases where a property of a protocol appear to be not used, mainly where these are constants set on construction, which are not used in any permissions or obligations, but which are of interest to the outside world when the protocol state as a whole is fetched using an API call, GraphQL query, or streamed.

Would it be possible to add something like const rather than var to indicate this?

Or is this type of thing indeed an anti-pattern - using protocols as entities?

[pierre]

At present it is technically possible (as workaround) to “copy” the value of a non-var constructor argument to a non-var protocol field at instantiation, but you will get warning “W0012: Declarations without ‘var’ are no longer allowed and will be removed in an upcoming release.”