roconnor-blockstream

Results 158 comments of roconnor-blockstream

I created this patch because I was trying to understand where CompCert was relying on proof irrelevance. In my experience, proof irrelevance is usually not necessary. I consider using proof...

Your comments are fair. I believe that you will eventually come to regret accepting non-proof irrelevent definitions in `Prop`, such as `perm_order` in your development if you start making more...

Is there a workaround to avoid this crash, beyond simply not building documentation?

Building my [project](https://github.com/ElementsProject/simplicity) under GHC 9.2 (and 9.4). More specifically the `runhaskell Setup.lhs haddock` command fails in the end with the error haddock: internal error: haddock:iface CallStack (from HasCallStack): error,...

Sorry. I should have written `Setup.hs`. `cabal haddock` does appear to work.

Using `runhaskell Setup.hs haddock` executes /nix/store/4zpfpnwflsrpf1lmnnx9jkdypzpz2b1j-ghc-9.2.3-with-packages/bin/haddock '@dist/doc/html/Simplicity/haddock-response287381-7.txt' while using `cabal haddock` /nix/store/4zpfpnwflsrpf1lmnnx9jkdypzpz2b1j-ghc-9.2.3-with-packages/bin/haddock '@/home/roconnor/Simplicity/dist-newstyle/build/x86_64-linux/ghc-9.2.3/Simplicity-0.0.0/l/Simplicity-Indef/doc/html/Simplicity/haddock-response286953-1.txt' But these response files are cleaned up right away so I cannot view them. Is there a...

the `--keep-temp-files` flag works with `runhaskell Setup.hs`, however I haven't figured out where to place `haddock-keep-temp-files: True` to make it work with `cabal haddock`. One thing to observe is that...

I wouldn't say I have a reasonable experience. I make due with making a manual index.html, and even then, all the problems in https://github.com/haskell/haddock/issues/1363 persist (plus now it is simply...

One design choice I made was to eliminate witnesses programs whose length is less than 10 bytes from being addressable by this segwit address scheme. My reasoning here is that...

Based on feedback I received here and elsewhere, I now understand that the issues surrounding `bc1` addresses is far more complicated that I realized. The information below was gathered from...