-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[Proposal] Support named bind parameters #199
Comments
With call-site hygiene stabilized in 1.45, the explicit binding could actually be omitted: let name = 320;
query!("select ?name"); |
Should this be closed in favor of #875? That one has a bunch more comments. |
This is a related issue of supporting named parameters in general. Implementing #875 would close both issues. |
Is there any update on named bindings? |
Not really, otherwise this issue would be closed, or that progress would be linked to this issue. In case your company needs this, you could also consider sponsoring @abonander (I don't speak for launchbadge or Austin => have no inside intel if that is an option, but that should likely be taken offline anyway..) |
@Flamenco, i would love to see this as a crate :D |
The text was updated successfully, but these errors were encountered: