You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 28, 2017. It is now read-only.
@Ichoran (and others from the discussion at scala/slip#28 (comment)) have a fairly valid point that the current names for safe/fast can be confusing
He suggested something like strict/permissive, from
@mdedetrich - I'd suggest "strict" and ("lax" or "permissive"). That gives you a better idea of what the use cases are. "mapped" and "raw" would be my second choices. Maybe you can come up with others, but I think the existing names have demonstrated themselves as not being good enough. It'd be better to name them sqyrg and ziskob than what they're lableled now, as then people would be forced to read the docs to figure out what the distinctions are.
The text was updated successfully, but these errors were encountered:
mdedetrich
changed the title
Change name from fast/safe to something else
Change name from fast/safe to something else
Nov 6, 2015
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
@Ichoran (and others from the discussion at scala/slip#28 (comment)) have a fairly valid point that the current names for safe/fast can be confusing
He suggested something like strict/permissive, from
The text was updated successfully, but these errors were encountered: