idris-lang/Idris2
1
1
Fork 0
mirror of https://github.com/idris-lang/Idris2.git synced 2024-12-20 18:21:47 +03:00
Code Issues Projects Releases Wiki Activity
88a5328ec1
Idris2/tests/ttimp/dot001/expected

16 lines
743 B
Plaintext
Raw Normal View History

Add test script They don't all pass yet, for minor reasons. Coming shortly... Unfortunately the startup overhead for chez is really noticeable here!
2020-05-19 20:25:18 +03:00
Processing as TTImp
Written TTC
Yaffle> Bye for now!
Processing as TTImp
[ new ] `--install-with-src`; refactoring around `FC`s (#1450) Why: * To implement robust cross-project go-to-definition in LSP i.e you can jump to definition of any global name coming from library dependencies, as well as from the local project files. What it does: * Modify `FC`s to carry `ModuleIdent` for .idr sources, file name for .ipkg sources or nothing for interactive runs. * Add `--install-with-src` to install the source code alongside the ttc binaries. The source is installed into the same directory as the corresponding ttc file. Installed sources are made read-only. * As we install the sources pinned to the related ttc files we gain the versioning of sources for free.
2021-06-05 14:53:22 +03:00
Dot2:15:1--16:1:When elaborating left hand side of Main.half:
Cumulativity preparation: Add field for universe level to TType (#2076) * Add field for universe level to TType This doesn't do anything yet, other than introduce new universe variables whenever we introduce a new type, but it's the first step towards checking the universe hierarchy. Next step is to add constraints when checking pi, unifying/converting types, and when adding data constructors. * TTC version increment Thought I'd done this, but apparently I didn't save the file. Oops! * Add structure for universe constraints * Fix display of ambiguity errors We need to store the Context in errors at the point where the error occurs, or we might get some nonsense in the message. There's still a couple of places in Error where we don't do this right. This fixes one of them, and improves a few messages in the process.
2021-10-31 02:00:16 +03:00
Dot2:15:28--15:30:Pattern variable {P:n:393} unifies with ?{P:m:393}_[]
Add test script They don't all pass yet, for minor reasons. Coming shortly... Unfortunately the startup overhead for chez is really noticeable here!
2020-05-19 20:25:18 +03:00
Yaffle> Bye for now!
Processing as TTImp
[ new ] `--install-with-src`; refactoring around `FC`s (#1450) Why: * To implement robust cross-project go-to-definition in LSP i.e you can jump to definition of any global name coming from library dependencies, as well as from the local project files. What it does: * Modify `FC`s to carry `ModuleIdent` for .idr sources, file name for .ipkg sources or nothing for interactive runs. * Add `--install-with-src` to install the source code alongside the ttc binaries. The source is installed into the same directory as the corresponding ttc file. Installed sources are made read-only. * As we install the sources pinned to the related ttc files we gain the versioning of sources for free.
2021-06-05 14:53:22 +03:00
Dot3:18:1--19:1:When elaborating left hand side of Main.addBaz3:
Cumulativity preparation: Add field for universe level to TType (#2076) * Add field for universe level to TType This doesn't do anything yet, other than introduce new universe variables whenever we introduce a new type, but it's the first step towards checking the universe hierarchy. Next step is to add constraints when checking pi, unifying/converting types, and when adding data constructors. * TTC version increment Thought I'd done this, but apparently I didn't save the file. Oops! * Add structure for universe constraints * Fix display of ambiguity errors We need to store the Context in errors at the point where the error occurs, or we might get some nonsense in the message. There's still a couple of places in Error where we don't do this right. This fixes one of them, and improves a few messages in the process.
2021-10-31 02:00:16 +03:00
Dot3:18:10--18:15:Can't match on ($resolved365 ?{P:x:404}_[] ?{P:x:404}_[]) (Not a constructor application or primitive) - it elaborates to ($resolved365 ?Main.{_:53}_[] ?Main.{_:54}_[])
Add test script They don't all pass yet, for minor reasons. Coming shortly... Unfortunately the startup overhead for chez is really noticeable here!
2020-05-19 20:25:18 +03:00
Yaffle> Bye for now!
Processing as TTImp
[ new ] `--install-with-src`; refactoring around `FC`s (#1450) Why: * To implement robust cross-project go-to-definition in LSP i.e you can jump to definition of any global name coming from library dependencies, as well as from the local project files. What it does: * Modify `FC`s to carry `ModuleIdent` for .idr sources, file name for .ipkg sources or nothing for interactive runs. * Add `--install-with-src` to install the source code alongside the ttc binaries. The source is installed into the same directory as the corresponding ttc file. Installed sources are made read-only. * As we install the sources pinned to the related ttc files we gain the versioning of sources for free.
2021-06-05 14:53:22 +03:00
Dot4:17:1--18:1:When elaborating left hand side of Main.addBaz4:
Cumulativity preparation: Add field for universe level to TType (#2076) * Add field for universe level to TType This doesn't do anything yet, other than introduce new universe variables whenever we introduce a new type, but it's the first step towards checking the universe hierarchy. Next step is to add constraints when checking pi, unifying/converting types, and when adding data constructors. * TTC version increment Thought I'd done this, but apparently I didn't save the file. Oops! * Add structure for universe constraints * Fix display of ambiguity errors We need to store the Context in errors at the point where the error occurs, or we might get some nonsense in the message. There's still a couple of places in Error where we don't do this right. This fixes one of them, and improves a few messages in the process.
2021-10-31 02:00:16 +03:00
Dot4:17:33--17:34:Can't match on ?{P:x:406}_[] (Non linear pattern variable) - it elaborates to ?Main.{dotTm:55}_[]
Add test script They don't all pass yet, for minor reasons. Coming shortly... Unfortunately the startup overhead for chez is really noticeable here!
2020-05-19 20:25:18 +03:00
Yaffle> Bye for now!
Reference in New Issue Copy Permalink