decentral1se/tasty-discover 36
Haskell test discovery for the tasty framework :eyes:
matsubara0507/awesome-backpack 4
A collection of awesome Backpack of Haskell links.
Pure Lisp on D Language
Chrome extension for bookmark using GitHub
The ChatWork API for Haskell
matsubara0507/anaqram-server 2
Score Ranking Server for AnaQRam with Haskell Servant
Framework for Slack Bot based on Events API by Ruby
matsubara0507/curry-howard-linebot 2
LINE Bot that replay Curry-Howard Isomorphism with paper
Dhall + exports (+ extend)
AWS 用に書いたコード置き場
push eventmatsubara0507/my-github-cards
commit sha 2dce42de122ee11c3c0c6cad57066cca352b82eb
[skip ci] Update docs by selfcat
push time in 4 hours
starteddaikimiura/rocker
started time in 5 hours
startedjongio/memealyzer
started time in 5 hours
push eventghc/ghc
commit sha 6c131ba04ab1455827d985704e4411aa19185f5f
DerivingVia for Hsc instances. GND for NonDetFastString and LexicalFastString.
commit sha a2e4cb80db1b63ea2c5e0ab501acec7fb1b116e3
HsUniToken and HsToken for HsArrow (#19623) Another step towards a simpler design for exact printing. Updates the haddock submodule.
commit sha 01fd26178f2c7ccbddbd66387e21f339cf9cda96
profiling: Look in RHS of rules for cost centre ticks There are some obscure situations where the RHS of a rule can contain a tick which is not mentioned anywhere else in the program. If this happens you end up with an obscure linker error. The solution is quite simple, traverse the RHS of rules to also look for ticks. It turned out to be easier to implement if the traversal was moved into CoreTidy rather than at the start of code generation because there we still had easy access to the rules. ./StreamD.o(.text+0x1b9f2): error: undefined reference to 'StreamK_mkStreamFromStream_HPC_cc' ./MArray.o(.text+0xbe83): error: undefined reference to 'StreamK_mkStreamFromStream_HPC_cc' Main.o(.text+0x6fdb): error: undefined reference to 'StreamK_mkStreamFromStream_HPC_cc'
commit sha d8bfebec6340ee5e1aa6f1731d5c4b91d8377fdb
Corrected typo
commit sha 34484c89ac1a5f037ec7f423c72d3cb4b830b831
Remove the backend correction logic, as it is already been fixed at this point
commit sha e25772a0a95fc9b606044e1afae31ff84790838a
PPC NCG: Fix panic in linear register allocator
commit sha a83d29995d096cca1ceff7042b73080db69219cf
Fix error message for record updates, #19972 Fix found by Adam Gundry.
commit sha a0622459f1d9a7068e81b8a707ffc63e153444f8
Move validate-x86_64-linux-deb9-hadrian back to quick-build This increases the critical path length but in practice will reduce pressure on runners because less jobs overall will be spawned. See #20003 [skip ci]
commit sha 2b415c4fbe6db1803467dd6193d889cf2fae2c93
Optimiser: Correctly deal with strings starting with unicode characters in exprConApp_maybe For example: "\0" is encoded to "C0 80", then the rule would correct use a decoding function to work out the first character was "C0 80" but then just used BS.tail so the rest of the string was "80". This resulted in "\0" being transformed into '\C0\80' : unpackCStringUTF8# "80" Which is obviously bogus. I rewrote the function to call utf8DecodeByteString directly and avoid the roundtrip through Faststring so now the head/tail is computed by the same call. It's quite hard to come up with a test for this as you need to engineer a strict context to make the exprConApp_maybe case to fire. Fixes #19976
push time in 6 hours
PR opened commercialhaskell/stackage
@bgamari Since your language-dot repo has issue-tracking disabled, this is the easiest way I see to request that you add language-dot to Stackage.
I've been using it in Cubix for a while, and now wish to use it in another project. A very cursory glance suggests that language-dot is superior to dot.
This awaits only your approval.
(This is a follow-up to https://github.com/commercialhaskell/stackage/pull/6070 , since recreating the PR was easier than altering the old one to accommodate changes to Stackage.)
Checklist:
-
[x] Meaningful commit message, eg
add my-cool-package(please not mentionbuild-constraints.yml) -
[x] At least 30 minutes have passed since uploading to Hackage
-
[x] On your own machine, you have successfully run the following command (find verify-package in the root of this repo):
./verify-package $package # or $package-$version
The script runs virtually the following commands in a clean directory:
stack unpack $package-$version # `-$version` is optional
cd $package-$version
rm -f stack.yaml && stack init --resolver nightly --ignore-subdirs
stack build --resolver nightly --haddock --test --bench --no-run-benchmarks
pr created time in 6 hours
PR closed commercialhaskell/stackage
@bgamari Since your language-dot repo has issue-tracking disabled, this is the easiest way I see to request that you add language-dot to Stackage.
I've been using it in Cubix for a while, and now wish to use it in another project. A very cursory glance suggests that language-dot is superior to dot.
This awaits only your approval.
Checklist:
-
[x] Meaningful commit message, eg
add my-cool-package(please not mentionbuild-constraints.yml) -
[x] At least 30 minutes have passed since uploading to Hackage
-
[x] On your own machine, you have successfully run the following command (find verify-package in the root of this repo):
./verify-package $package # or $package-$version
The script runs virtually the following commands in a clean directory:
stack unpack $package-$version # `-$version` is optional
cd $package-$version
rm -f stack.yaml && stack init --resolver nightly --ignore-subdirs
stack build --resolver nightly --haddock --test --bench --no-run-benchmarks
pr closed time in 6 hours
push eventghc/ghc
commit sha a0622459f1d9a7068e81b8a707ffc63e153444f8
Move validate-x86_64-linux-deb9-hadrian back to quick-build This increases the critical path length but in practice will reduce pressure on runners because less jobs overall will be spawned. See #20003 [skip ci]
commit sha d0680897d5a4cda487e667a7e97f809da79d8789
Set min LLVM version to 9 and make version checking use a non-inclusive upper bound. We use a non-inclusive upper bound so that setting the upper bound to 13 for example means that all 12.x versions are accepted.
push time in 6 hours
startedmatsubara0507/gasdump
started time in 7 hours
startedranjitjhala/sprite-lang
started time in 7 hours
startedExtremaIS/literatex-haskell
started time in 8 hours
startedExtremaIS/ttc-haskell
started time in 8 hours
PR opened commercialhaskell/stackage
geniplate-mirror 0.7.8 has been updated for GHC 9.0.1, see https://hackage.haskell.org/package/geniplate-mirror-0.7.8 and CI results https://github.com/danr/geniplate/runs/2855322960?check_suite_focus=true.
Checklist:
-
[X] Meaningful commit message, eg
add my-cool-package(please not mentionbuild-constraints.yml) -
[X] At least 30 minutes have passed since uploading to Hackage
-
[X] On your own machine, you have successfully run the following command (find verify-package in the root of this repo):
./verify-package $package # or $package-$version
The script runs virtually the following commands in a clean directory:
stack unpack $package-$version # `-$version` is optional
cd $package-$version
rm -f stack.yaml && stack init --resolver nightly --ignore-subdirs
stack build --resolver nightly --haddock --test --bench --no-run-benchmarks
pr created time in 8 hours
push eventghc/ghc
commit sha 719cada1b081ff77153cdfbf7629d7f121a315ad
Add Shifts for subwords
push time in 9 hours
create barnchghc/ghc
branch : wip/angerman/aarch64-shift-improvements
created branch time in 9 hours
fork azu/squoosh
Make images smaller using best-in-class codecs, right in the browser.
fork in 10 hours
issue commentcommercialhaskell/stackage
Messaging on FAQ for New GHC release timing
Hello! :) Did this thread result in any doc updates for setting expectations around the lag in reflecting a compiler release. The README mentions:
The lag for minor ghc releases should be less but it still requires extra work and there is usually some delay - this also allows for some community testing before updating LTS.
That was for the LTS release though. What would be the timeframe for something like the nightly build's current compiler version of 8.10.4 bumped to the recent 8.10.5 point release? Thanks in advance! :)
comment created time in 11 hours
startedalvaroloes/enumer
started time in 11 hours
startedCysharp/CsprojModifier
started time in 12 hours
created repositoryazu/top-ceo-chart
Glassdoor's Top CEO charts. Annual transition
created time in 12 hours
PR closed ghc-proposals/ghc-proposals
DynFlags hampers the modularity of GHC.
Instead of referring to it directly, refer to a type parameter constrained to have just the information necessary.
The benefits of this are somewhat uncertain, so merge the refactor on an experimental basis, and revert it if they aren't realized.
Rendered WIP MR: https://gitlab.haskell.org/ghc/ghc/merge_requests/1033
CC @wz1000 @bgamari
pr closed time in 13 hours
pull request commentghc-proposals/ghc-proposals
WIP: Don't speak of `DynFlags`
Thanks to @hsyl20 a lot of this has already happened, and continues to happen.
comment created time in 13 hours
push eventghc/ghc
commit sha f4a5e30e7b027894535872164df50c300d8e6b0f
Do not add unfoldings to lambda-binders For reasons described in GHC.Core.Opt.Simplify Historical Note [Case binders and join points], we used to keep a Core unfolding in one of the lambda-binders for a join point. But this was always a gross hack -- it's very odd to have an unfolding in a lambda binder, that refers to earlier lambda binders. The hack bit us in various ways: * Most seriously, it is incompatible with linear types in Core. * It complicated demand analysis, and could worsen results * It required extra care in the simplifier (simplLamBinder) * It complicated !5641 (look for "join binder unfoldings") So this patch just removes the hack. Happily, doind so turned out to have no effect on performance.
commit sha 8baa8874935daae7d2b7c6f5a1215a379b8b85db
User's Guide: reword and fix punctuation in description of PostfixOperators
commit sha fb6b6379efcc07c6b5fd00368310f204f4a5f7bc
Add (broken) test for #19966
commit sha 61c51c00b6e12e309bc5643e89330b93d86f5449
Fix redundant import
commit sha 472c2bf003e9f3bb93b82265f2a0a7124f944421
Reword: representation instead of levity fixes #19756, updates haddock submodule
commit sha 3d5cb3352c1e1c20f0d5de427f4edbc765ce06d6
Fix INLINE pragmas in desugarer In #19969 we discovered that GHC has has a bug *forever* that means it sometimes essentially discarded INLINE pragams. This happened when you have * Two more more mutually recursive functions * Some of which (presumably not all!) have an INLINE pragma * Completely monomorphic. This hits a particular case in GHC.HsToCore.Binds.dsAbsBinds, which was simply wrong -- it put the INLINE pragma on the wrong binder. This patch fixes the bug, rather easily, by adjusting the no-tyvar, no-dict case of GHC.HsToCore.Binds.dsAbsBinds. I also discovered that the GHC.Core.Opt.Pipeline.shortOutIndirections was not doing a good job for {-# INLINE lcl_id #-} lcl_id = BIG gbl_id = lcl_id Here we want to transfer the stable unfolding to gbl_id (we do), but we also want to remove it from lcl_id (we were not doing that). Otherwise both Ids have large stable unfoldings. Easily fixed. Note [Transferring IdInfo] explains.
commit sha 2a7e29e5303058473484b10ed57d3c579d78fe83
gitlab-ci: Bump ci-images
commit sha 6c131ba04ab1455827d985704e4411aa19185f5f
DerivingVia for Hsc instances. GND for NonDetFastString and LexicalFastString.
commit sha a2e4cb80db1b63ea2c5e0ab501acec7fb1b116e3
HsUniToken and HsToken for HsArrow (#19623) Another step towards a simpler design for exact printing. Updates the haddock submodule.
commit sha 01fd26178f2c7ccbddbd66387e21f339cf9cda96
profiling: Look in RHS of rules for cost centre ticks There are some obscure situations where the RHS of a rule can contain a tick which is not mentioned anywhere else in the program. If this happens you end up with an obscure linker error. The solution is quite simple, traverse the RHS of rules to also look for ticks. It turned out to be easier to implement if the traversal was moved into CoreTidy rather than at the start of code generation because there we still had easy access to the rules. ./StreamD.o(.text+0x1b9f2): error: undefined reference to 'StreamK_mkStreamFromStream_HPC_cc' ./MArray.o(.text+0xbe83): error: undefined reference to 'StreamK_mkStreamFromStream_HPC_cc' Main.o(.text+0x6fdb): error: undefined reference to 'StreamK_mkStreamFromStream_HPC_cc'
commit sha d8bfebec6340ee5e1aa6f1731d5c4b91d8377fdb
Corrected typo
commit sha 34484c89ac1a5f037ec7f423c72d3cb4b830b831
Remove the backend correction logic, as it is already been fixed at this point
commit sha e25772a0a95fc9b606044e1afae31ff84790838a
PPC NCG: Fix panic in linear register allocator
commit sha a83d29995d096cca1ceff7042b73080db69219cf
Fix error message for record updates, #19972 Fix found by Adam Gundry.
commit sha a0622459f1d9a7068e81b8a707ffc63e153444f8
Move validate-x86_64-linux-deb9-hadrian back to quick-build This increases the critical path length but in practice will reduce pressure on runners because less jobs overall will be spawned. See #20003 [skip ci]
commit sha 12970bfc8cda19cab8cc49f723b44d514bb40a85
Deprecate -Wmissing-monadfail-instances (#17875) Also document deprecation of Wnoncanonical-monadfail-instances and -Wimplicit-kind-vars
push time in 16 hours
push eventghc/ghc
commit sha f4a5e30e7b027894535872164df50c300d8e6b0f
Do not add unfoldings to lambda-binders For reasons described in GHC.Core.Opt.Simplify Historical Note [Case binders and join points], we used to keep a Core unfolding in one of the lambda-binders for a join point. But this was always a gross hack -- it's very odd to have an unfolding in a lambda binder, that refers to earlier lambda binders. The hack bit us in various ways: * Most seriously, it is incompatible with linear types in Core. * It complicated demand analysis, and could worsen results * It required extra care in the simplifier (simplLamBinder) * It complicated !5641 (look for "join binder unfoldings") So this patch just removes the hack. Happily, doind so turned out to have no effect on performance.
commit sha 8baa8874935daae7d2b7c6f5a1215a379b8b85db
User's Guide: reword and fix punctuation in description of PostfixOperators
commit sha fb6b6379efcc07c6b5fd00368310f204f4a5f7bc
Add (broken) test for #19966
commit sha 61c51c00b6e12e309bc5643e89330b93d86f5449
Fix redundant import
commit sha 472c2bf003e9f3bb93b82265f2a0a7124f944421
Reword: representation instead of levity fixes #19756, updates haddock submodule
commit sha 3d5cb3352c1e1c20f0d5de427f4edbc765ce06d6
Fix INLINE pragmas in desugarer In #19969 we discovered that GHC has has a bug *forever* that means it sometimes essentially discarded INLINE pragams. This happened when you have * Two more more mutually recursive functions * Some of which (presumably not all!) have an INLINE pragma * Completely monomorphic. This hits a particular case in GHC.HsToCore.Binds.dsAbsBinds, which was simply wrong -- it put the INLINE pragma on the wrong binder. This patch fixes the bug, rather easily, by adjusting the no-tyvar, no-dict case of GHC.HsToCore.Binds.dsAbsBinds. I also discovered that the GHC.Core.Opt.Pipeline.shortOutIndirections was not doing a good job for {-# INLINE lcl_id #-} lcl_id = BIG gbl_id = lcl_id Here we want to transfer the stable unfolding to gbl_id (we do), but we also want to remove it from lcl_id (we were not doing that). Otherwise both Ids have large stable unfoldings. Easily fixed. Note [Transferring IdInfo] explains.
commit sha 2a7e29e5303058473484b10ed57d3c579d78fe83
gitlab-ci: Bump ci-images
commit sha 6c131ba04ab1455827d985704e4411aa19185f5f
DerivingVia for Hsc instances. GND for NonDetFastString and LexicalFastString.
commit sha a2e4cb80db1b63ea2c5e0ab501acec7fb1b116e3
HsUniToken and HsToken for HsArrow (#19623) Another step towards a simpler design for exact printing. Updates the haddock submodule.
commit sha 01fd26178f2c7ccbddbd66387e21f339cf9cda96
profiling: Look in RHS of rules for cost centre ticks There are some obscure situations where the RHS of a rule can contain a tick which is not mentioned anywhere else in the program. If this happens you end up with an obscure linker error. The solution is quite simple, traverse the RHS of rules to also look for ticks. It turned out to be easier to implement if the traversal was moved into CoreTidy rather than at the start of code generation because there we still had easy access to the rules. ./StreamD.o(.text+0x1b9f2): error: undefined reference to 'StreamK_mkStreamFromStream_HPC_cc' ./MArray.o(.text+0xbe83): error: undefined reference to 'StreamK_mkStreamFromStream_HPC_cc' Main.o(.text+0x6fdb): error: undefined reference to 'StreamK_mkStreamFromStream_HPC_cc'
commit sha d8bfebec6340ee5e1aa6f1731d5c4b91d8377fdb
Corrected typo
commit sha 34484c89ac1a5f037ec7f423c72d3cb4b830b831
Remove the backend correction logic, as it is already been fixed at this point
commit sha e25772a0a95fc9b606044e1afae31ff84790838a
PPC NCG: Fix panic in linear register allocator
commit sha a83d29995d096cca1ceff7042b73080db69219cf
Fix error message for record updates, #19972 Fix found by Adam Gundry.
commit sha a0622459f1d9a7068e81b8a707ffc63e153444f8
Move validate-x86_64-linux-deb9-hadrian back to quick-build This increases the critical path length but in practice will reduce pressure on runners because less jobs overall will be spawned. See #20003 [skip ci]
commit sha 059eb35105d8061a2bc52122771bb5e72c38d364
Typos, minor comment fixes - Remove fstName, sndName, fstIdKey, sndIdKey - not used - Fix typos in comments - Remove outdated comment in Lint.hs - Use 'LitRubbish' instead of 'RubbishLit' for consistency - Remove comment about subkinding - superseded by Note [Kind Constraint and kind Type] - Mention ticket ID in a linear types error message - Fix formatting in using-warnings.rst and linear-types.rst - Remove comment about 'Any' in Dynamic.hs - Dynamic now uses Typeable + existential instead of Any - Remove codeGen/should_compile/T13233.hs This was added by accident, it is not used and T13233 is already in should_fail
push time in 16 hours