Lots of name shadowed warnings in query wrappers
See original GitHub issueBuild Environment SQLDelight version: 1.4.3 OS: macOS Gradle version: 6.6 Kotlin version: 1.4.10 AGP Version (if applicable):
Describe the bug
As a result of #1926, the parameter names of the generated lambda often shadow the parameter names of the enclosing function. This results in lots of Name shadowed
warnings. If this isn’t easily fixable or is intended, it would be great to generate a @Suppress
for these.
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (8 by maintainers)
Top Results From Across the Web
Remove warning about shadowed value names? · Issue #3375
There are definite valid reasons for wanting to shadow names - for example, often I want to hide an old version of a...
Read more >Unnecessary "Name shadowed" warning on parameter of ...
Unnecessary "Name shadowed" warning on parameter of local function or local class member. This reproduces on 1.1. 3-dev-1637, but does not reproduce on...
Read more >What is the problem with shadowing names defined in outer ...
I append the variable names with an underscore just to clear this warning so I ... for query in queries: res = twitter.search(query)...
Read more >XSL Transformations (XSLT) Version 3.0 - W3C
Abstract. This specification defines the syntax and semantics of XSLT 3.0, a language designed primarily for transforming XML documents into ...
Read more >32 SWIG and Python
For example, if the input file is example.i, the name of the wrapper file is example_wrap.c. ... example.i:11: Warning 509: as it is...
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
Any chance that can be reconsidered? My project is blocked on updating to Kotlin 1.4 by this, because we have the “treat warnings as errors” option enabled.
Not sure if the fact that I caused the issue helps or hurts my request 😬
No plans for that, no.