Skip to content

Conversation

@chrysn
Copy link
Contributor

@chrysn chrysn commented Apr 28, 2020

This would allow having both the regular (never-panicking unless #4 is triggered) kind of slots instances and instances that use a different kind of key (currently an unwrapped usize, could just as well get a more scary name and From<>/Into<> implementations) where keys are not guaranteed to be usable.

This is work in progress and not meant as an immediate fix, rather as an illustration for the discussion at #2.

chrysn added 2 commits April 28, 2020 10:31
This moves the main key functionality into a trait, and makes Key<...>
the default key used by Slots.

This will later enable non-enforced keys, and could be extended to other
forms of authentication of keys.
@bugadani bugadani marked this pull request as draft April 28, 2020 08:59
@bugadani
Copy link
Owner

Marked as draft before I accidentally merge this

@bugadani
Copy link
Owner

I think #10 would be a nicer solution

@chrysn
Copy link
Contributor Author

chrysn commented Apr 29, 2020

Better than this approach at any rate, closing this.

@chrysn chrysn closed this Apr 29, 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.

2 participants