Releases: scalacenter/tasty-query
Releases · scalacenter/tasty-query
v0.10.4
v0.10.3
v0.10.2
v0.10.1
v0.10.0
- Replace
Span
s bySourcePosition
. When coming from a tasty file with source line information, aSourcePosition
can provide line and column number, in addition to offset and file name. Lambda.meth
is now statically aTermReferenceTree
.- Add the abstract class
Traversers.TreeTraverser
to walk trees with more control thanTree.walkTree
.
v0.9.3
v0.9.2
v0.9.1
v0.9.0
This release makes a number of breaking changes to adhere more closely to the Scala 3 specification, as well as to have a clearer API.
- Reorganize the
Type
hierarchy:- A
Type
is now only what the spec calls a type. Methodic types, wildcard type args and package refs are excluded from it. - Introduce
TypeOrMethodic
for the type of term definitions. - Introduce
TypeOrWildcard
for the arguments ofAppliedType
s. TermType
is the type assigned to term expressions:Type
,MethodicType
orPackageRef
.- Rename
WildcardTypeBounds
toWildcardTypeArg
.
- A
- Introduce "primitive"
NothingType
andAnyKindType
. The membersscala.Nothing
andscala.AnyKind
are type aliases to the underlying primitive types. - Remove
Symbol.flags
andSymbol.privateWithin
. Instead, introduce a number of dedicated, semantic accessors such asTermOrTypeSymbol.visibility
orTermSymbol.isSetter
. Type.baseType(ClassSymbol)
follows the spec more closely.- Expose whether method types are
using
orimplicit
clauses (asMethodType.isContextual
andisImplicit
, respectively). - Remove the
(using Context)
from a number of API methods. Those methods, by construction, guarantee that they work without loading anything from the classpath. They constitute the API that is safe to use without a semantically complete classpath.