From sanzhiyan at gmail.com Thu Mar 7 11:18:44 2019 From: sanzhiyan at gmail.com (Andrea Vezzosi) Date: Thu, 7 Mar 2019 11:18:44 +0100 Subject: [Agda-dev] Signature in Closure type Message-ID: Hi, I was looking at the Closure type in .Base and saw that it stores a signature. data Closure a = Closure { clSignature :: Signature , clEnv :: TCEnv , clScope :: ScopeInfo , clModuleCheckpoints :: Map ModuleName CheckpointId , clValue :: a } deriving (Data, Functor, Foldable) However `enterClosure` does not use it, in fact no code ever looks at it, you can change the field type to `()`, adapt `buildClosure`, and remove `getMetaSig` and everything still compiles. For my use-case not restoring the `Signature` is what I want anyway, so things work fine. However, should we remove this field to avoid retaining useless signatures? Or should we be worried that signatures are not being restored when they ought to be? -- Andrea From Jesper at sikanda.be Sun Mar 10 02:20:21 2019 From: Jesper at sikanda.be (Jesper Cockx) Date: Sun, 10 Mar 2019 02:20:21 +0100 Subject: [Agda-dev] Signature in Closure type In-Reply-To: References: Message-ID: I would guess that we don't restore the signature because we are expecting/hoping some kind of monotonicity property to hold, i.e. adding new things to the signature doesn't change which definitions typecheck that don't mention these new things. But I'm not sure why we need to store it at all, it seems it goes back a very long way. Feel free to experiment with what happens if you remove it. -- Jesper On Thu, Mar 7, 2019 at 11:19 AM Andrea Vezzosi wrote: > Hi, > > I was looking at the Closure type in .Base and saw that it stores a > signature. > > data Closure a = Closure > { clSignature :: Signature > , clEnv :: TCEnv > , clScope :: ScopeInfo > , clModuleCheckpoints :: Map ModuleName CheckpointId > , clValue :: a > } > deriving (Data, Functor, Foldable) > > However `enterClosure` does not use it, in fact no code ever looks at > it, you can change the field type to `()`, adapt `buildClosure`, and > remove `getMetaSig` and everything still compiles. > > For my use-case not restoring the `Signature` is what I want anyway, > so things work fine. > > However, should we remove this field to avoid retaining useless signatures? > Or should we be worried that signatures are not being restored when > they ought to be? > > -- Andrea > _______________________________________________ > 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 Mar 15 13:41:32 2019 From: asr at eafit.edu.co (Andres Sicard Ramirez) Date: Fri, 15 Mar 2019 12:41:32 +0000 Subject: [Agda-dev] [ANNOUNCE] Agda 2.6.0 release candidate 1 Message-ID: Dear all, The Agda Team is very pleased to announce the first release candidate of Agda 2.6.0. Installation ======= This RC can be installed using the following instructions: $ cabal install https://hackage.haskell.org/package/Agda-2.5.4.2.20190310/candidate/Agda-2.5.4.2.20190310.tar.gz or $ cabal get https://hackage.haskell.org/package/Agda-2.5.4.2.20190310/candidate/Agda-2.5.4.2.20190310.tar.gz $ cd Agda-2.5.4.2.20190310 $ cabal install GHC supported versions =============== This RC has been tested with GHC 8.6.4, 8.4.4, 8.2.2, 8.0.2 and 7.10.3 on Linux, macOS and Windows. 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, fixed issues and incompatibilities ================================ * http://hackage.haskell.org/package/Agda-2.5.4.2.20190310/candidate/changelog * New option `--cubical` to enable support for path equality and related features from Cubical Type Theory (https://arxiv.org/abs/1611.02108), including univalence and higher inductive types. See `Cubical` in the documentation for more info. Enjoy the RC and please test as much as possible. -- Andr?s, on behalf of the Agda Team From abela at chalmers.se Thu Mar 28 17:05:19 2019 From: abela at chalmers.se (Andreas Abel) Date: Thu, 28 Mar 2019 17:05:19 +0100 Subject: [Agda-dev] Run the testsuite before pushing to master Message-ID: <162f557a-277f-6deb-395a-2a3d1b023900@chalmers.se> Folks, don't forget your manners: - before pushing to master, run the testsuite through - if you want travis take care of this, work with pull requests If you think you can predict whether the testsuite will run through cleanly after your changes, let me assure you, you are most likely wrong. I have been there many times. Best, Andreas -- Andreas Abel <>< Du bist der geliebte Mensch. Department of Computer Science and Engineering Chalmers and Gothenburg University, Sweden andreas.abel at gu.se http://www.cse.chalmers.se/~abela/ From abela at chalmers.se Sat Mar 30 09:04:02 2019 From: abela at chalmers.se (Andreas Abel) Date: Sat, 30 Mar 2019 09:04:02 +0100 Subject: [Agda-dev] Issue label de-Bruijn Message-ID: Dear Agda developers, if you encounter an issue with de Bruijn indices, please tag it with label de-Bruijn Getting data on how many bugs are caused by wrong de Bruijn indices will help us evaluate the pros and cons of a dependently-typed representation of terms with well-scoped de Bruijn indices. Thanks, Andreas -- Andreas Abel <>< Du bist der geliebte Mensch. Department of Computer Science and Engineering Chalmers and Gothenburg University, Sweden andreas.abel at gu.se http://www.cse.chalmers.se/~abela/