Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Investigate the Shared_Message accessibility issue #64

Open
mosteo opened this issue Sep 17, 2024 · 0 comments
Open

Investigate the Shared_Message accessibility issue #64

mosteo opened this issue Sep 17, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@mosteo
Copy link
Contributor

mosteo commented Sep 17, 2024

When using an access discriminant, on instantiation. Very obscure reason:

--  Element allocator may need an accessibility check in case actual type
--  is class-wide or has access discriminants (RM 4.8(10.1) and
--  AI12-0035).

Ideally, having the access discriminant allowed for implicit dereferencing, which has been lost (.Msg accessor instead).
@mosteo mosteo added the enhancement New feature or request label Sep 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mosteo