idris-lang/Idris2
1
1
Fork 0
mirror of https://github.com/idris-lang/Idris2.git synced 2024-12-19 09:12:34 +03:00
Code Issues Projects Releases Wiki Activity
7692de67aa
Idris2/tests/chez/chez031/expected

32 lines
1.2 KiB
Plaintext
Raw Normal View History

add specifier check for cli compilation Missed a case which is covered now by checking for exceptions where postOptions is used add *> <* to Core
2020-09-14 00:20:50 +03:00
Error: The given specifier was not accepted by any backend. Available backends:
[ new ] Add `chez-sep` codegen (#1359) Co-authored-by: Johann Rudloff <johann@sinyax.net>
2021-05-11 10:20:19 +03:00
chez, chez-sep, racket, node, javascript, refc, gambit
add nicer errors for bad specifiers
2020-09-13 01:51:01 +03:00
Some backends have additional specifier rules, refer to their documentation.
[ 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
Specifiers:29:1--30:35
add specifier check for cli compilation Missed a case which is covered now by checking for exceptions where postOptions is used add *> <* to Core
2020-09-14 00:20:50 +03:00
29 | %foreign "scheme,racket:+"
30 | plusRacketFail : Int -> Int -> Int
Error: The given specifier was not accepted by any backend. Available backends:
[ new ] Add `chez-sep` codegen (#1359) Co-authored-by: Johann Rudloff <johann@sinyax.net>
2021-05-11 10:20:19 +03:00
chez, chez-sep, racket, node, javascript, refc, gambit
add specifier check for cli compilation Missed a case which is covered now by checking for exceptions where postOptions is used add *> <* to Core
2020-09-14 00:20:50 +03:00
Some backends have additional specifier rules, refer to their documentation.
[ 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
Specifiers:29:1--30:35
[ cosmetic ] nicer error messages for uncaught exceptions
2021-03-25 15:02:28 +03:00
29 | %foreign "scheme,racket:+"
30 | plusRacketFail : Int -> Int -> Int
add nicer errors for bad specifiers
2020-09-13 01:51:01 +03:00
Main> Loaded file Specifiers.idr
Specifiers> Error: The given specifier was not accepted by any backend. Available backends:
[ new ] Add `chez-sep` codegen (#1359) Co-authored-by: Johann Rudloff <johann@sinyax.net>
2021-05-11 10:20:19 +03:00
chez, chez-sep, racket, node, javascript, refc, gambit
add nicer errors for bad specifiers
2020-09-13 01:51:01 +03:00
Some backends have additional specifier rules, refer to their documentation.
[ 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
Specifiers:29:1--30:35
add nicer errors for bad specifiers
2020-09-13 01:51:01 +03:00
Specifiers> [exec] Specifiers> Error: The given specifier was not accepted by any backend. Available backends:
[ new ] Add `chez-sep` codegen (#1359) Co-authored-by: Johann Rudloff <johann@sinyax.net>
2021-05-11 10:20:19 +03:00
chez, chez-sep, racket, node, javascript, refc, gambit
add nicer errors for bad specifiers
2020-09-13 01:51:01 +03:00
Some backends have additional specifier rules, refer to their documentation.
[ 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
Specifiers:29:1--30:35
add nicer errors for bad specifiers
2020-09-13 01:51:01 +03:00
[exec] Specifiers>
Bye for now!
Reference in New Issue Copy Permalink