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.

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

Deprecate 'Map.these' instead of marking it unstable #21733

Merged
merged 4 commits into from
Mar 2, 2023

Conversation

bmcdonald3
Copy link
Member

@bmcdonald3 bmcdonald3 commented Mar 2, 2023

Previously, 'Map.these' was marked unstable since we are planning on changing the behavior to yield (const ref, ref) instead of just the keys, but we've decided that a deprecation makes more sense than an unstable mark.

  • paratest

Previously, 'Map.these' was marked unstable since we are planning
on changing the behavior to yield (const ref, ref) instead of just
the keys, but we've decided that a deprecation makes more sense
than an unstable mark.

Signed-off-by: Ben McDonald <46734217+bmcdonald3@users.noreply.github.com>
Signed-off-by: Ben McDonald <46734217+bmcdonald3@users.noreply.github.com>
Signed-off-by: Ben McDonald <46734217+bmcdonald3@users.noreply.github.com>
Copy link
Member

@lydia-duncan lydia-duncan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think there's some DistributedMap draft updates needed but other than that this looks good! Thanks

Signed-off-by: Ben McDonald <46734217+bmcdonald3@users.noreply.github.com>
@bmcdonald3 bmcdonald3 merged commit 85c3070 into chapel-lang:main Mar 2, 2023
@bmcdonald3 bmcdonald3 deleted the map-dep branch March 2, 2023 17:39
bradcray added a commit to bradcray/chapel that referenced this pull request Mar 3, 2023
(watch out for those #21x33 PRs, kids!)

This fixes a few futures that I must've missed in my last paratest run
(prior to paratest running futures by default!) as well as an obvious
problem with the test of the bash autocompletion which I'm not sure
how it slipped past me.

It also fixes an issue from Ben McDonald's chapel-lang#21733 which I happened to
notice since he's likely out for the evening.

While here, I noticed that an erroneous condition that I'd noted
earlier in chapel-lang#21652 has been resolved, probably by chapel-lang#21614 as Michael
predicted, so I added a compopts line to lock that behavior in (and
removed another that, in retrospect, felt overly paranoid).

---
Signed-off-by: Brad Chamberlain <bradcray@users.noreply.github.com>
bradcray added a commit that referenced this pull request Mar 3, 2023
[trivial, not reviewed]

This fixes a few futures that I must've missed in my last paratest run
(prior to paratest running futures by default!) as well as an obvious
problem with the test of the bash autocompletion which I'm not sure how
it slipped past me.

It also fixes an issue from Ben McDonald's #21733 which I happened to
notice since he's likely out for the evening.

While here, I noticed that an erroneous condition that I'd noted earlier
in #21652 has been resolved, probably by #21614 as Michael predicted, so
I added a compopts line to lock that behavior in (and removed another
that, in retrospect, felt overly paranoid).
bmcdonald3 added a commit that referenced this pull request Mar 3, 2023
[ trivial, not reviewed ]

'map.items()' was deprecated in #21733 in favor of zipping over 
the keys and values, so this updates the protobuf code to follow 
that recommendation.
bmcdonald3 added a commit to bmcdonald3/chapel that referenced this pull request Mar 3, 2023
In chapel-lang#21733, I had updated submitted benchmarks rather than updating
their good files so that we remember to go and update the submitted
files. This PR undoes the changes that were made and updates the
good files to reflect the deprecations.

Signed-off-by: Ben McDonald <46734217+bmcdonald3@users.noreply.github.com>
bmcdonald3 added a commit to bmcdonald3/chapel that referenced this pull request Mar 3, 2023
In chapel-lang#21733, I had updated submitted benchmarks rather than updating
their good files so that we remember to go and update the submitted
files. This PR undoes the changes that were made and updates the
good files to reflect the deprecations.

Signed-off-by: Ben McDonald <46734217+bmcdonald3@users.noreply.github.com>
bmcdonald3 added a commit that referenced this pull request Mar 6, 2023
In #21733, I had updated submitted benchmarks rather than updating their
good files so that we remember to go and update the submitted files.
This PR undoes the changes that were made and updates the good files to
reflect the deprecations.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants