`for<'lifetime>` formatting issue
See original GitHub issueCurrently (rust plugin v0.0.1.866-nightly) thing like where F: for<'b> Fn(...)
are reformatted to where F: for < 'b > Fn(...)
which is a bit ugly and inconsistent with type parameters formatting in other cases (in impl
, struct
/trait
, fn
they are condensed).
Would you change default formatting for this case and add an option in Code style -> Rust
if it’s really needed for someone.
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Need to prevent GC for lifetime of M/R job · Issue #209 · apache/fluo ...
Work done on #8 made the Fluo GC iter collect based on what Transactions are currently active. When using this Fluo input format...
Read more >Python format() - Programiz
The format() function returns a formatted representation of a given value specified by the format specifier. Example 1: Number formatting with format(). #...
Read more >Date format issue to save giftcard Lifetime in Magento 2
If I get value for LifeTime as $lifetime = date('18/11/2020');. Then ExpiryDate is not set and is shown as no expiry for that...
Read more >API Reference — fmt 9.1.0 documentation
A view of a collection of formatting arguments. To avoid lifetime issues it should only be used as a parameter type in type-erased...
Read more >rust - Why can't print a struct field with formatted print?
Your problem is not a formatting problem, just an issue with what exactly println! accepts in its formatting string.
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
@matklad, if you ping back this issue after grammar changes I’ll test plugin nightly build (which I’m currently on) and report the result.
Thanks for the great report!