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

Make Swift Concurrently compatible by removing use of ThreadSpecificVariable #106

Closed
wants to merge 1 commit into from

Conversation

danpalmer
Copy link

I've been using a fork from @noli-ai that has been deleted or made private. This contained several fixes. In the interests of giving visibility to those fixes I'm opening this PR to address an issue that another committer found. This is not my work, but I am depending on these fixes in order to make Imperial usable in an async codebase.

Unfortunately I don't know much about the details of the changes – the commit/PR title is the only documentation I have available.

If there are small changes necessary to get this merged I'm happy to make them, but if this requires more work I'd rather leave this PR open for others who may need it until such time as #88 / #94 / #100 land.

@0xTim
Copy link
Member

0xTim commented Jul 31, 2024

Just an FYI I'm going to be doing an Imperial code sprint next week to go through all the issues and PRs

@0xTim
Copy link
Member

0xTim commented Dec 12, 2024

Closing in favour of #109

@0xTim 0xTim closed this Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants