From Jesper at sikanda.be Fri May 18 10:53:54 2018 From: Jesper at sikanda.be (Jesper Cockx) Date: Fri, 18 May 2018 10:53:54 +0200 Subject: [Agda-dev] Why do we support cpp? Message-ID: Hi all, Maybe I'm beating a dead horse here, but why do we still also support cpp instead of only cpphs if cpp can't even properly handle primes (')? This is extremely annoying and hits me in >50% of the cases when I push something. I know about the issue where 'build-depends' in the cabal file doesn't automatically install the dependencies, but couldn't we just add 'cabal install cpphs' to the makefile and drop support for cpp? This seems like a much better solution than polluting our code with {-'-} or additional line breaks. -- Jesper ps: sorry for the rant. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ulfn at chalmers.se Fri May 18 11:07:10 2018 From: ulfn at chalmers.se (Ulf Norell) Date: Fri, 18 May 2018 11:07:10 +0200 Subject: [Agda-dev] Why do we support cpp? In-Reply-To: References: Message-ID: FWIW I'm always building without cpphs, so I get the error before pushing. A reason not to switch to cpphs only is that we've been having lots of problems with it. A quick search on the issue tracker finds 40 issues mentioning cpphs. / Ulf On Fri, May 18, 2018 at 10:53 AM, Jesper Cockx wrote: > Hi all, > > Maybe I'm beating a dead horse here, but why do we still also support cpp > instead of only cpphs if cpp can't even properly handle primes (')? This is > extremely annoying and hits me in >50% of the cases when I push something. > I know about the issue where 'build-depends' in the cabal file doesn't > automatically install the dependencies, but couldn't we just add 'cabal > install cpphs' to the makefile and drop support for cpp? This seems like a > much better solution than polluting our code with {-'-} or additional line > breaks. > > -- Jesper > > ps: sorry for the rant. > > _______________________________________________ > Agda-dev mailing list > Agda-dev at lists.chalmers.se > https://lists.chalmers.se/mailman/listinfo/agda-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jesper at sikanda.be Fri May 18 11:42:50 2018 From: Jesper at sikanda.be (Jesper Cockx) Date: Fri, 18 May 2018 11:42:50 +0200 Subject: [Agda-dev] Why do we support cpp? In-Reply-To: References: Message-ID: I would argue that we *also* have a lot of problems with cpp, and the current approach gives us the worst of both worlds. BTW, how can I tell ghc to use cpp instead of cpphs just for one build? It seems I always get cpphs by default unless I uninstall it. -- Jesper On Fri, May 18, 2018 at 11:07 AM, Ulf Norell wrote: > FWIW I'm always building without cpphs, so I get the error before pushing. > A reason not to switch to cpphs only is that we've been having lots of > problems with it. A quick search on the issue tracker finds 40 issues > mentioning cpphs. > > / Ulf > > On Fri, May 18, 2018 at 10:53 AM, Jesper Cockx wrote: > >> Hi all, >> >> Maybe I'm beating a dead horse here, but why do we still also support cpp >> instead of only cpphs if cpp can't even properly handle primes (')? This is >> extremely annoying and hits me in >50% of the cases when I push something. >> I know about the issue where 'build-depends' in the cabal file doesn't >> automatically install the dependencies, but couldn't we just add 'cabal >> install cpphs' to the makefile and drop support for cpp? This seems like a >> much better solution than polluting our code with {-'-} or additional line >> breaks. >> >> -- Jesper >> >> ps: sorry for the rant. >> >> _______________________________________________ >> Agda-dev mailing list >> Agda-dev at lists.chalmers.se >> https://lists.chalmers.se/mailman/listinfo/agda-dev >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ulfn at chalmers.se Fri May 18 11:46:57 2018 From: ulfn at chalmers.se (Ulf Norell) Date: Fri, 18 May 2018 11:46:57 +0200 Subject: [Agda-dev] Why do we support cpp? In-Reply-To: References: Message-ID: make CABAL_OPTS=--flags=-cpphs / Ulf On Fri, May 18, 2018 at 11:42 AM, Jesper Cockx wrote: > I would argue that we *also* have a lot of problems with cpp, and the > current approach gives us the worst of both worlds. > > BTW, how can I tell ghc to use cpp instead of cpphs just for one build? It > seems I always get cpphs by default unless I uninstall it. > > -- Jesper > > On Fri, May 18, 2018 at 11:07 AM, Ulf Norell wrote: > >> FWIW I'm always building without cpphs, so I get the error before >> pushing. A reason not to switch to cpphs only is that we've been having >> lots of problems with it. A quick search on the issue tracker finds 40 >> issues mentioning cpphs. >> >> / Ulf >> >> On Fri, May 18, 2018 at 10:53 AM, Jesper Cockx wrote: >> >>> Hi all, >>> >>> Maybe I'm beating a dead horse here, but why do we still also support >>> cpp instead of only cpphs if cpp can't even properly handle primes (')? >>> This is extremely annoying and hits me in >50% of the cases when I push >>> something. I know about the issue where 'build-depends' in the cabal file >>> doesn't automatically install the dependencies, but couldn't we just add >>> 'cabal install cpphs' to the makefile and drop support for cpp? This seems >>> like a much better solution than polluting our code with {-'-} or >>> additional line breaks. >>> >>> -- Jesper >>> >>> ps: sorry for the rant. >>> >>> _______________________________________________ >>> Agda-dev mailing list >>> Agda-dev at lists.chalmers.se >>> https://lists.chalmers.se/mailman/listinfo/agda-dev >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From asr at eafit.edu.co Fri May 18 13:33:27 2018 From: asr at eafit.edu.co (=?UTF-8?B?QW5kcsOpcyBTaWNhcmQtUmFtw61yZXo=?=) Date: Fri, 18 May 2018 06:33:27 -0500 Subject: [Agda-dev] Why do we support cpp? In-Reply-To: References: Message-ID: Hi Jesper, On 18 May 2018 at 03:53, Jesper Cockx wrote: > Maybe I'm beating a dead horse here, but why do we still also support cpp > instead of only cpphs if cpp can't even properly handle primes (')? This is > extremely annoying and hits me in >50% of the cases when I push something. I > know about the issue where 'build-depends' in the cabal file doesn't > automatically install the dependencies, but couldn't we just add 'cabal > install cpphs' to the makefile and drop support for cpp? This seems like a > much better solution than polluting our code with {-'-} or additional line > breaks. We switched from cpp to cpphs due to some issues on OS X, but since cpphs didn't work in all the configurations (see https://github.com/agda/agda/issues/1285 ) we need to support both. Best, -- Andr?s From asr at eafit.edu.co Sat May 19 22:33:18 2018 From: asr at eafit.edu.co (=?UTF-8?B?QW5kcsOpcyBTaWNhcmQtUmFtw61yZXo=?=) Date: Sat, 19 May 2018 15:33:18 -0500 Subject: [Agda-dev] [ANNOUNCE] Agda 2.5.4 release candidate 1 Message-ID: Dear all, The Agda Team is very pleased to announce the first release candidate of Agda 2.5.4. We plan to release 2.5.4 in one week. Installation ======= This RC can be installed using the following instruction: $ cabal install http://hackage.haskell.org/package/Agda-2.5.3.20180519/candidate/Agda-2.5.3.20180519.tar.gz GHC supported versions =============== This RC has been tested with GHC 7.10.3, 8.0.2, 8.2.2 and 8.4.2 on Linux, macOS and Windows. Please note that GHC 8.4.2 requires cabal-install ? 2.2.0.0. Standard library ========== For the time being, you can use the `experimental` branch of the standard library which is compatible with this RC. This branch is available at https://github.com/agda/agda-stdlib/ What is new, some fixed issues and incompatibilities ================================ http://hackage.haskell.org/package/Agda-2.5.3.20180519/candidate/changelog Enjoy the RC and please test as much as possible. -- Andr?s, on behalf of the Agda Team From asr at eafit.edu.co Sat May 26 07:20:46 2018 From: asr at eafit.edu.co (=?UTF-8?B?QW5kcsOpcyBTaWNhcmQtUmFtw61yZXo=?=) Date: Sat, 26 May 2018 00:20:46 -0500 Subject: [Agda-dev] [ANNOUNCE] Agda 2.5.4 release candidate 2 Message-ID: Dear all, The Agda Team is very pleased to announce the second release candidate of Agda 2.5.4. We plan to release 2.5.4 in one week. Fixed issues on this RC ============== The fixed issues since the first release candidate were: #2306: Commands in the emacs-mode get confused if we add question marks to the file #3004: Agda hangs on extended lambda #3067: checking hangs on invalid program #3072: invalid section printing #3074: Wrong hiding causes internal error in LHS checker #3075: Automatic inlining and tactics #3078: Error building with GHC 7.10.2: Missing transformers library #3079: Wrong parameter hiding for instance open #3080: Case splitting prints out-of-scope pattern synonyms #3082: Emacs mode regression: a ? inserted before existing hole hijacks its interaction point #3083: Wrong hiding in module application #3084: Changes to mode line do not take effect immediately #3085: Postpone checking a pattern let binding when type is blocked Installation ======= This RC can be installed using the following instruction: $ cabal install https://hackage.haskell.org/package/Agda-2.5.3.20180526/candidate/Agda-2.5.3.20180526.tar.gz GHC supported versions =============== This RC has been tested with GHC 7.10.3, 8.0.2, 8.2.2 and 8.4.2 on Linux, macOS and Windows. Please note that GHC 8.4.2 requires cabal-install ? 2.2.0.0. Standard library ========== For the time being, you can use the `experimental` branch of the standard library which is compatible with this RC. This branch is available at https://github.com/agda/agda-stdlib/tree/experimental What is new, some fixed issues and incompatibilities ================================ https://hackage.haskell.org/package/Agda-2.5.3.20180526/candidate/changelog Enjoy the RC and please test as much as possible. -- Andr?s, on behalf of the Agda Team From ulf.norell at gmail.com Mon May 28 17:35:12 2018 From: ulf.norell at gmail.com (Ulf Norell) Date: Mon, 28 May 2018 17:35:12 +0200 Subject: [Agda-dev] Old issues and the icebox Message-ID: As you may have noticed, depending on your github email settings, I'm going through all issues and either assigning them a milestone or closing them. The purpose of this exercise, aside from it being lots and lots of fun, is to prevent future issues from slipping through the cracks. We'll have - "milestone: (future-version)" for issues we are at least going to consider before releasing (future-version) - "milestone: icebox" for issues we have no current plans of looking at - no milestone for issues we need to look at and decide which of the above applies I've also removed priority:low and priority:medium, and plan to remove priority:high and priority:highest once I'm done. Basically, low and medium are subsumed by the icebox and high/highest by the milestone for the next release. I'm keeping priority:critical for things we really should fix right away. Some of my decisions on what issues to close or which milestone to apply are somewhat arbitrary, so don't hesitate to protest when you disagree (except you Andreas if it's something to do with syntax). / Ulf -------------- next part -------------- An HTML attachment was scrubbed... URL: