| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
| |
This required a major change in the way positions are handled, as the
previous scheme did not allow to read the positions of arbitrary subtrees
selectively.
Fortunately, it's altogether a major simplification.
Also, this fixed a bug in the previous scheme, where positions were
generated before compactification, resulting in addresses being wrong.
|
| |
|
|
|
|
|
| |
Instead of separate source file sections, pickle SourceFile as an
annotation of all toplevel classes.
We represent it like this anyway when reading back Tasty-defined classes.
|
| |
|
|
|
| |
`isTyper` is used to enable some error checking and handling, which
need not be done when in FromTasty.
|
| |
|
|
|
| |
Makes side-effecting initialization of interpreter
unnecessary.
|
| | |
|
| |
|
|
|
| |
Reporters are part of the context which is passed into a compiler run. Passing them
as a separate option is an unnecessary complication.
|
| | |
|
| |
|
|
|
|
|
| |
The pickling package got rather large and confusing with three
separate tasks that each had their own conventions: read JVM classfiles,
read Scala2 pickle info, read Tasty. The classes for each task are now in
separate packages.
|
| |
|
|
|
| |
We want to ensure that the whole tree is read at phase
frontend. To achieve this, we run an empty traverser over the tree.
|
| | |
|
| |
|
|
|
|
| |
A missing delta position signifies that the node has
the same position as its parent. Once that case was
added, we can now enable positions when reading from Tasty.
|
| |
|
|
|
|
|
| |
So far: Only one source file is recorded. Should evaluate
whether more are needed. Will programs composed from several
source files be pickled? They will certainly be generated after
inlining, but maybe all that happens after pickling?
|
|
|
`FromTasty` is a main module which compiles TASTY info instead of sources.
|
