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
bound methods #141
Labels
proposal
This issue suggests modifications. If it also has the "accepted" label then it is planned.
Milestone
Comments
thejoshwolfe
added
the
enhancement
Solving this issue will likely involve adding new logic or components to the codebase.
label
Apr 20, 2016
Is this still necessary given the new generic syntax? const bound_next_func: fn.(&Rand)->u32 = if (preferences.safety) rand.next_safe else rand.next_unsafe;
bound_next_func(); // equivalent to `bound_next_func.func(bound_next_func.this)` How about instead: const nextFunc = if (preferences.safety) Rand.nextSafe else Rand.nextUnsafe;
nextFunc(rand); |
Closed
This was referenced Feb 6, 2017
andrewrk
added
proposal
This issue suggests modifications. If it also has the "accepted" label then it is planned.
and removed
enhancement
Solving this issue will likely involve adding new logic or components to the codebase.
labels
Mar 14, 2019
This was referenced Apr 19, 2020
The new plan is to get rid of the BoundFn type. I think this is possible now that we have |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
proposal
This issue suggests modifications. If it also has the "accepted" label then it is planned.
The text was updated successfully, but these errors were encountered: