-
Notifications
You must be signed in to change notification settings - Fork 425
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.
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
Adding entries to map of shared type results in an error #14713
Comments
FYI map aficionado @dlongnecke-cray |
This seems potentially related to a number of other collection + managed class orthogonality issues:
I'm tracking this list in https://github.com/Cray/chapel-private/issues/643 and have added this issue to that list. |
The coercion from var nillableN: Node? = n;
children.add('key', nillableN); |
Adds several new tests that are related to previous issues/bugs which were filed and are no longer broken on main. ## New Tests - `classes/delete-free/shared/shared-in-map-list.chpl` - Test for #14713 - `classes/deinitializers/owned-with-deinit.chpl` - Test for #12973 - `classes/fields/type-resolve-array-field.chpl` - Test for #11421 - `arrays/intents/in/defaultValueWithInIntent.chpl` - Test for #11424 - `classes/errors/newWithoutParen.chpl` - Test for #13201 - `functions/lambda/lambdaCapturing.chpl` - Test for #5544 - `library/standard/Map/getBorrowFromFunc.chpl` - Test for #14370 ## Testing - local testing --- [Reviewed by @lydia-duncan ] closes #14713 closes #12973 closes #11421 closes #11424 closes #13201 closes #5544 closes #14370
Summary of Problem
Adding to a map with a value of
shared
type, results in an error inMap.chpl
.My current work-around is to stick to
unmanaged
for now. (owned
andborrowed
have separate issues: #14712)Steps to Reproduce
Source Code:
Error message:
I found that this can be fixed by modifying the
add
signature inMap.chpl
:changed to:
However, I have not done testing beyond my user code with this fix.
Configuration Information
chpl --version
: chpl version 1.21.0 pre-release (4f4e862)The text was updated successfully, but these errors were encountered: