polysemy-research/polysemy
1
1
Fork 0
mirror of https://github.com/polysemy-research/polysemy.git synced 2024-12-02 02:43:39 +03:00
Code Issues Projects Releases Wiki Activity
4a5f2ce92a
polysemy/stack.yaml

19 lines
332 B
YAML
Raw Normal View History

I AM THE KING BRAIN LORD also fintan
2019-03-03 02:55:19 +03:00
resolver: lts-13.0
GLORY
2019-02-13 23:52:56 +03:00
packages:
- .
plugin
2019-04-21 01:31:17 +03:00
- polysemy-plugin
GLORY
2019-02-13 23:52:56 +03:00
core-dump
2019-03-18 04:03:23 +03:00
extra-deps:
Don't emit the FirstOrder error for unknown effects (#115) This PR introduces the FCF machinery that will give us more control over writing type-level functions. It defines an IfStuck a b c tyfam that will leave b around if a is stuck, otherwise it will fcf-evaluate c. Everything is polykinded so we can stack these things together to make big logic chains to emit specific variables depending on what exactly is stuck.
2019-06-17 00:14:36 +03:00
- aeson-1.4.3.0
- bifunctors-5.5.4
core-dump
2019-03-18 04:03:23 +03:00
- dump-core-0.1.3.2
Don't emit the FirstOrder error for unknown effects (#115) This PR introduces the FCF machinery that will give us more control over writing type-level functions. It defines an IfStuck a b c tyfam that will leave b around if a is stuck, otherwise it will fcf-evaluate c. Everything is polykinded so we can stack these things together to make big logic chains to emit specific variables depending on what exactly is stuck.
2019-06-17 00:14:36 +03:00
- first-class-families-0.5.0.0
it is so FAST
2019-03-18 22:50:19 +03:00
- ghc-lib-0.20190204
Fixes #54 (#85)
2019-06-05 16:44:34 +03:00
- inspection-testing-0.4.2
Use new, separate `loopbreaker` library for inlining (#145) * Remove explicit loopbreakers, enable plugin * Use uploaded version of `loopbreaker` * Fix span of macro * Disable plugin on GHC <8.6 * Add comment about use of plugin * Separate unrelated conditions
2019-07-01 09:13:37 +03:00
- loopbreaker-0.1.1.0
Don't emit the FirstOrder error for unknown effects (#115) This PR introduces the FCF machinery that will give us more control over writing type-level functions. It defines an IfStuck a b c tyfam that will leave b around if a is stuck, otherwise it will fcf-evaluate c. Everything is polykinded so we can stack these things together to make big logic chains to emit specific variables depending on what exactly is stuck.
2019-06-17 00:14:36 +03:00
- monadLib-3.9
- th-abstraction-0.3.1.0
Forklift interpretations (#128) This PR provides a single function withLowerToIO, which runs a desired Sem r effect all the way down to IO, without needing to know the natural transformation beforehand. It does it by running the desired code in a new thread, and shipping all of the unhandled effects back to the main thread. The main thread turns into an event loop for the duration of the withLowerToIO block.
2019-06-26 06:46:54 +03:00
- unagi-chan-0.4.1.0
Use type-errors for our type errors! (#144) This PR has farmed out the type error machinery out to my new package https://github.com/isovector/type-errors. It's much nicer to work with, and a big red diff!
2019-07-03 23:05:51 +03:00
- type-errors-0.2.0.0
Add Final Effect (#217) * Add Final Effect * Changes per review, Final at top-level, doc changes * Update Changelog * Final touches to Final * Revert change to stack.yaml
2019-08-30 23:38:53 +03:00
- type-errors-pretty-0.0.0.0
Reference in New Issue Copy Permalink