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 map_to and update_flags unsafe #135

Merged
merged 5 commits into from Apr 11, 2020
Merged

Conversation

phil-opp
Copy link
Member

@phil-opp phil-opp commented Mar 6, 2020

Fixes #134

This is a breaking change.

@phil-opp phil-opp added this to the 0.10.0 milestone Apr 10, 2020
@phil-opp phil-opp force-pushed the make-map_to_unsafe-again branch 2 times, most recently from a41e3a8 to 78ddc43 Compare Apr 11, 2020
@phil-opp phil-opp force-pushed the make-map_to_unsafe-again branch from 78ddc43 to 604a79b Compare Apr 11, 2020
@phil-opp phil-opp force-pushed the make-map_to_unsafe-again branch from 604a79b to 985d6db Compare Apr 11, 2020
@phil-opp phil-opp changed the title Make map_to unsafe again Make map_to and update_flags unsafe Apr 11, 2020
@phil-opp phil-opp marked this pull request as ready for review Apr 11, 2020
@phil-opp phil-opp merged commit 177bb41 into master Apr 11, 2020
5 checks passed
@phil-opp phil-opp deleted the make-map_to_unsafe-again branch Apr 11, 2020
phil-opp added a commit that referenced this pull request Apr 11, 2020
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.

The map_to function should be unsafe
2 participants