Skip to content

Add shuttle-parking_lot#232

Merged
jorajeev merged 3 commits intomainfrom
parking_lot
Mar 26, 2026
Merged

Add shuttle-parking_lot#232
jorajeev merged 3 commits intomainfrom
parking_lot

Conversation

@sarsko
Copy link
Copy Markdown
Contributor

@sarsko sarsko commented Nov 22, 2025

Adds Shuttle support for the parking_lot library


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@@ -0,0 +1,20 @@
[package]
name = "shuttle-parking_lot"
version = "0.0.1"
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This should be "0.12.5" right?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Debatable, I think no.

In my head releasing version mirrors is independent from the code. Thus all wrappers will be pushed as 0.0.1, because this is a releasable non-colliding version for all the packages, meaning we can release it and depend on it without there being any confusion on what version its wrapping. We can also yank a version 0.0.1 that was released (accidentally or not) without any loss. It is thus "safe" to have version 0.0.1. Version "0.12.5" however has a version collision, and publishing it is a final action. It is not "safe" to have version 0.12.5.

Regardless of what we release, I think the crates should live in the repo as 0.0.1s

@@ -0,0 +1,22 @@
[package]
name = "shuttle-rand"
version = "0.0.1"
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Should be 0.8 no?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Same as the comment on the parking lot version

@sarsko
Copy link
Copy Markdown
Contributor Author

sarsko commented Nov 26, 2025

The original plan was to use #233 to resolve the issue with poisoned locks. Upon further investigation this does not work, and we need to expose a lock which doesn't poison from Shuttle. Put up an issue here #237

@sarsko
Copy link
Copy Markdown
Contributor Author

sarsko commented Jan 12, 2026

All comments should be addressed

@sarsko sarsko force-pushed the parking_lot branch 4 times, most recently from 6782e63 to 248d293 Compare January 12, 2026 23:43
@sarsko sarsko force-pushed the parking_lot branch 2 times, most recently from a83bc17 to 34899ca Compare February 4, 2026 00:36
Copy link
Copy Markdown
Member

@jorajeev jorajeev left a comment

Choose a reason for hiding this comment

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

Also add a README similar to what we have for tokio (see https://github.com/awslabs/shuttle/blob/main/wrappers/tokio/README.md )?

@sarsko sarsko force-pushed the parking_lot branch 2 times, most recently from fbd44aa to 388689a Compare February 17, 2026 12:02
@jorajeev jorajeev merged commit 1adf67f into main Mar 26, 2026
7 checks passed
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