Re: Gitlab slow?

2022-11-14 Thread Hécate
I believe we can get a long way with enabling tracing in our GitLab instance, especially since Grafana can be used for visualisation, through its associated product Tempo (which is compatible with Jaeger). https://docs.gitlab.com/ee/development/distributed_tracing.html Le 14/11/2022 à 17:33,

Re: Gitlab slow?

2022-11-14 Thread Ben Gamari
Bryan Richter via ghc-devs writes: > I find it very slow, as well. :( > > Eventually I want to be able to help out with these problems, but > right now my priorities are different and I don't have the bandwidth. > We rely on Ben still. (I am at least relieving him of other tasks that > would be

Re: Status of Stream Fusion?

2022-11-14 Thread Sebastian Graf
Yes, if you confine yourself to Miller's "pattern fragment" (Meta variables may appear in the head of an application, but then the arguments may only be *distinct* bound variables) then you might be fine. Thanks for giving it a try! Am Mo., 14. Nov. 2022 um 14:27 Uhr schrieb J. Reinders <

Re: Status of Stream Fusion?

2022-11-14 Thread J. Reinders
I think higher order pattern unification is different from higher order matching because the unification means both sides are allowed to be patterns that may contain meta variables, while matching works on only one pattern and one concrete term. The example pattern ‘forall a. someFunction (\x

Re: Status of Stream Fusion?

2022-11-14 Thread Sebastian Graf
> I believe the reason that this is easier than higher order matching in general because it is restricted to applications of unification variables to locally bound variables. Indeed, it is easier to confine oneself to the pattern fragment. I think that's entirely the point of pattern unification:

Re: Status of Stream Fusion?

2022-11-14 Thread J. Reinders
Thank you both for the quick responses. > Can you say precisely what you mean by "using stream fusion instead of > foldr/build fusion in base"? For example, do you have a prototype library > that demonstrates what you intend, all except concatMap? I believe the stream-fusion library [1] and

Re: Gitlab slow?

2022-11-14 Thread Bryan Richter via ghc-devs
I find it very slow, as well. :( Eventually I want to be able to help out with these problems, but right now my priorities are different and I don't have the bandwidth. We rely on Ben still. (I am at least relieving him of other tasks that would be competing for his time!) On Mon, Nov 14, 2022

Gitlab slow?

2022-11-14 Thread Simon Peyton Jones
Is it just me, or is GitLab taking an unusually long time to serve up pages when looking at GHC tickets? Simon ___ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: Status of Stream Fusion?

2022-11-14 Thread Simon Peyton Jones
Jaro 1. Is the ‘concatMap’ problem really the only problem left on the way to > using stream fusion instead of foldr/build fusion in base? > Can you say precisely what you mean by "using stream fusion instead of foldr/build fusion in base"? For example, do you have a prototype library that

Re: Status of Stream Fusion?

2022-11-14 Thread Sebastian Graf
Hi Jaro, I'm very glad that you are interested in picking up the pieces I left behind! Re: SpecConstr: Yes, that pass is already moderately complicated and gets much more complicated when you start specialisation for non-bound lambdas, because that would need higher-order pattern unification in

Status of Stream Fusion?

2022-11-14 Thread J. Reinders
Dear GHC devs, I’m interested in stream fusion and would like to see what it takes to fix the remaining issues, so that it can replace foldr/build fusion in base. First of all I would like to know what exactly the challenges are that are left. I believe one of the main remaining problems is