RFC: Remove `attribute` parameter from fields
See original GitHub issueIssue Analytics
- State:
- Created 4 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
RFC: replace load_from and dump_to with a single parameter ...
Regarding the name of the new attribute, I think name is as unintuitive as key . I like field . My only concern:...
Read more >[RFC] Remove Types - MLIR - LLVM Discussion Forums
Step 1 would be to remove types from attributes, which itself would deduplicate a lot of code. But types and attributes would remain...
Read more >RFC 7644 - System for Cross-domain Identity Management
Standards Track [Page 29] RFC 7644 SCIM Protocol Specification September 2015 3.5.1. Replacing with PUT HTTP PUT is used to replace a resource's...
Read more >rfc2251.txt - » RFC Editor
Attribute Value A field of type AttributeValue takes on as its value either a string encoding of a AttributeValue data type, or an...
Read more >2565-formal-function-parameter-attributes - The Rust RFC Book
Conditional compilation with #[cfg(..)] is also facilitated by allowing more ergonomic addition and removal of parameters. Moreover, procedural macro authors ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It could make more sense just to discourage the use of
attribute
(and instead recommenddata_key
) in most cases, just to make the effective API surface area smaller.I guess, but that’s awkward. It feels wrong to set arbitrary attributes on an object.