This channel is now CLOSED. Please join us https://discord.com/invite/scala (scala-contributors channel)
or override one
I mean, export clauses that restrict the visibility of the exported definition. Something like,
private[akka] export obj.something
Found an answer at https://contributors.scala-lang.org/t/having-another-go-at-exports-pre-sip/2982/5
Sorry, I should've look there before asking.
Sorry, I should've look there before asking.
I was going to tweet about lampepfl/dotty#5923 but I feel like somebody from the Dotty team should do the shouting from the rooftops
What's the protocol for bringing in partest tests from scalac into dotty? I fixed an issue that is tested by the upstream test https://github.com/scala/scala/blob/2.13.x/test/files/run/t9516.scala: how do I port/enable that test into dotty, to test my fix?
So just copy the test and its checkfile into
tests/run?
psst, while you're looking at primitive ops in the backend, you might also want to port https://github.com/scala/scala/pull/7435/files :)
For the int-shift-long I needed the fixes in the constant-folder, and I couldn't reasonably fix the constant-foler but not the backend...
@smarter after watching a video on types in dotty, I was under the impression that something like
Function1[String, Int] was encoded as a RefinedType and not AppliedType, but looking into the codebase it looks like it is AppliedType after all. Also, the docs and the comments mention that each case in match type is either an unary function or a type lambda over unary function, but now there is some synthetic MatchCase type. Is it just implementation details or were there any underlying problems with previous encodings?
First, because we couldn't make it work well enough with higher-kinded types (https://infoscience.epfl.ch/record/222780/files/p51-odersky.pdf), then we tried to use it only for applying class types but it didn't seem worth it, and it made handling of wildcard applications more complicated (you want to be able to distinguish
C from C[_], but if you encode application as refinement you can't really do that)
Yes, eventually the spec will be updated
Is there a way to combine a new element onto the right of an existing tuple that doesn't cause this profligate nesting?
The last element must be Unit or a tuple
def f[A, B](a: A, b: B) = a *: b needs something to say that B is a type with *:
or more precisely, in Dotty the type (A,B) is syntactic sugar for the type
A *: B *: Unit
(Compile / compileIncremental) java.nio.file.NoSuchFileException: /drone/src/github.com/lampepfl/dotty/library/src-3.x/scala/Tuple.scala
shall I open an issue?
Unit is a type and () is the single instance of that type yes
not sure what you mean by symbol
Neither am I to be honest ;) I always mix up types and terms and symbols and those abstract words.
Well, Types are pretty obvious.
Also,
A *: () is totally kiss syntax