Comments (11)
Not sure what your board is, but feel free to ping me on questions / issues :)
from splain.
@tek patch is integrated a few days ago, closing
from splain.
this looks like a message from an annotation in that library
from splain.
don't think so, if it is an annotation it should come after the "invalid because" part.
Plus this annotation seems to be all types, no text. I knew PhD students are undisciplined, but not that undisciplined
from splain.
well then what is that NO PROOF
?
from splain.
Oh sorry that was part of the implicit annotation of shapesafe (the library I worked on)
from splain.
hmmm, looks like this problem can be triggered if the implicit function doesn't have a return type. The compiler has some weird rule in inferring and erasing type automatically in this case
from splain.
I found the cause of the problem, the following 2 types of Tree:
// TODO remove this class, add a tree attachment to Apply to track whether implicits were involved
// copying trees will all too easily forget to distinguish subclasses
class ApplyToImplicitArgs(fun: Tree, args: List[Tree]) extends Apply(fun, args)
// TODO remove this class, add a tree attachment to Apply to track whether implicits were involved
// copying trees will all too easily forget to distinguish subclasses
class ApplyImplicitView(fun: Tree, args: List[Tree]) extends Apply(fun, args)
May be returned as implicit candidate. Their .toString format is also very verbose (at least as verbose as TypeApply, which was replaced with an Apply when the error message is generated). So, the solution should be merely adding these 2 cases into the unapplyCandidate
A patch should be released shortly. But our end goal should be to merge it into scalac
from splain.
@tek do you think it is a good idea to invite @lrytz to be on our advisor board?
from splain.
if that is something he'd like to do, sure!
from splain.
Sounds good, let's finish the 1.0.0-RC1 for 2.13.6 first
from splain.
Related Issues (20)
- Compatibility with Java 8 is still sketchy on Gradle HOT 1
- Implicit search error should ideally explain type reduction process HOT 1
- Refined type signature may be hidden HOT 1
- Color was dropped but still exist in doc
- Unify integration/acceptance test formats across (Scala compiler) builtin cases & plugin cases
- Release countdown 1.0.3 HOT 2
- Release planning for 1.1.0
- Indented formats for Refined types and Tuple types
- Differentiating ambiguous type texts for type diff and type bound evidences HOT 1
- Attach existential context & alias annotations to type text on demand HOT 1
- Add instructions for scala CLI
- API/settings cleanup for new features added to 1.1.0 HOT 6
- reduction detail may display incorrect infix. HOT 2
- Long, multirow format for diff(found | required) HOT 3
- Diverging Implicit error in compact tree mode (without specifying `Vimplicits-verbose-tree`) reports some errors as "unlinked", while in reality they are just compacted HOT 3
- Release countdown for 1.0.1 HOT 2
- Publish 1.0.1 for scala 2.13.9 & 2.13.10 HOT 3
- Release binaries for latest 2.12 HOT 5
- 1.0.2 release countdown HOT 2
- Confused about difference between built in and 1.x HOT 6
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from splain.