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

Change OnceCell to OnceLock in TabExpandedString #694

Merged
merged 2 commits into from
Jan 28, 2025

Conversation

tgross35
Copy link
Contributor

The change at 1 stores some data in a OnceCell, which made ProgressStyle no longer Sync. Fix this by changing the OnceCell to a OnceLock, and add a static test that all relevant public types are Send and Sync.

The change at [1] stores some data in a `OnceCell`, which made
`ProgressStyle` no longer `Sync`. Fix this by changing the `OnceCell` to
a `OnceLock`, and add a static test that all relevant public types are
`Send` and `Sync`.

[1]: console-rs#684
@tgross35 tgross35 mentioned this pull request Jan 28, 2025
@djc
Copy link
Member

djc commented Jan 28, 2025

Mind adding a commit that bumps the version number to 0.17.11?

@tgross35
Copy link
Contributor Author

Sure, all set.

@djc djc merged commit fe59003 into console-rs:main Jan 28, 2025
10 checks passed
@djc
Copy link
Member

djc commented Jan 28, 2025

  • Published indicatif v0.17.11 at registry crates-io
  • [new tag] 0.17.11 -> 0.17.11
  • Release notes

@woodruffw
Copy link

Thanks a ton for fixing this so quickly! Out of curiosity, when should the release land on Crates.io?

@djc
Copy link
Member

djc commented Jan 28, 2025

Huh, looks like I managed to confuse myself with this morning's release! Published 0.17.11 now.

@woodruffw
Copy link

Thanks a ton!

@tgross35
Copy link
Contributor Author

Thanks for the quick review!

@tgross35 tgross35 deleted the progressstyle-sync branch January 28, 2025 19:34
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.

3 participants