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.

Sign up for GitHub

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

Jump to bottom

safety risk of .fetch/2 #80

Open
dckc opened this issue Apr 26, 2017 · 3 comments
Open

safety risk of .fetch/2 #80

dckc opened this issue Apr 26, 2017 · 3 comments

Comments

@dckc
Copy link
Member

dckc commented Apr 26, 2017 

<simpson> I feel like we need a space for documenting POLA maybe-not-safe-but-nobody-has-really-shown-a-good-PoC stuff.
<DanC_> PoC = proof of concept?
<simpson> Yeah.
 Stuff like .fetch/2 on Maps.
<DanC_> oh.
<DanC_> yes, the risk around .fetch/2 merits documenting. I'm raising an issue
@erights
Copy link

erights commented May 3, 2017

What is the safety risk or POLA violation of .fetch/2 ?

@dckc
Copy link
Member Author

dckc commented May 3, 2017

Something about f keeping a reference to k after m.fetch(k, f) I think.

@dckc
Copy link
Member Author

dckc commented Jul 14, 2017

http://wiki.erights.org/wiki/POLA_fetch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dckc @erights