gf-core.git/src/compiler/GF/Compile, branch masterUnnamed repository; edit this file 'description' to name the repository.
https://git.adelon.net/gf-core.git/atom?h=master2025-08-13T11:38:23+00:00add import Control.Monad when generating .hs with GADTs2025-08-13T11:38:23+00:00Inari Listenmaainari.listenmaa@gmail.com2025-08-13T11:38:23+00:00urn:sha1:9325c8f9fb54d1de1c16f946723a2716fd3fbd86define return in terms of pure, >> as *>, mappend as <>2025-08-02T14:39:31+00:00Inari Listenmaainari.listenmaa@gmail.com2024-09-09T17:43:39+00:00urn:sha1:b914a25de326dd937e3a1d05f4eefb46af6da7b4
In preparation for deprecation, see https://gitlab.haskell.org/ghc/ghc/-/wikis/proposal/semigroup-monoid and https://gitlab.haskell.org/ghc/ghc/-/wikis/proposal/monad-of-no-return
add whitespace on list comprehensions, applications etc.2025-08-02T14:39:31+00:00Inari Listenmaainari.listenmaa@gmail.com2024-09-09T17:38:27+00:00urn:sha1:1037b209ae225d5de604ff832d915c590ced4c38
text editor interprets these things as errors (e.g. unterminated qq for list comprehension) and underlines red, even though there is no real error.
Indent each line of an error message2023-09-25T07:55:02+00:00Andreas Källberganka.213@gmail.com2023-09-25T07:53:59+00:00urn:sha1:268a25f59cd4790ef5896ddd237f0bc48f6fad26
By indenting each line instead of just the first, we simplify
the work of the gf-lsp parser, so we can see which errors are the same
Clean up redundant case expressions2021-07-12T08:38:29+00:00Andreas Källberganka.213@gmail.com2021-07-12T08:38:29+00:00urn:sha1:7faf8c9dad5a88c38f7fa3633f8a1b286ac570c3Remove last traces of the Either in value2term2021-07-12T07:53:49+00:00Andreas Källberganka.213@gmail.com2020-11-29T14:03:08+00:00urn:sha1:b3881570c78cfc4596b64b9ef03463f6b74f1b19Remove the `Either Int` from value2term2021-07-12T07:50:43+00:00Andreas Källberganka.213@gmail.com2020-11-29T13:51:55+00:00urn:sha1:bd270b05ff92b15c15d5dfebd52576d0e15d0b04
This prevents HUGE space leak and makes compiling a PGF a LOT faster
For example, an application grammar moved from taking over 50GB
of ram and taking 5 minutes (most of which is spent on garbage colelction)
to taking 1.2 seconds and using 42mb of memory
The price we pay is that the "variable #n is out of scope" error is now
lazy and will happen when we try to evaluate the term instead of
happening when the function returns and allowing the caller to chose how
to handle the error.
I don't think this should matter in practice, since it's very rare;
at least Inari has never encountered it.
Fix bug introduced in cdbe73eb475cf44e1a45b2abacb12756e394016a2021-07-08T11:56:58+00:00John J. Camillerijohn@digitalgrammars.com2021-07-08T11:56:58+00:00urn:sha1:a1fd3ea142f215d7a030b8a95d32ba0c55dd61fb
Apparently I don't understand how pattern-matching works in Haskell
Remove two missing-methods warnings2021-07-08T10:10:41+00:00John J. Camillerijohn@digitalgrammars.com2021-07-08T10:10:41+00:00urn:sha1:cdbe73eb475cf44e1a45b2abacb12756e394016aReplace tabs for whitespace in source code2021-07-07T07:40:41+00:00John J. Camillerijohn@digitalgrammars.com2021-07-07T07:40:41+00:00urn:sha1:f2e52d6f2c2bc90febceebdea0268b40ea37476c