j3h

I ran into a bug that may or may not be the same, and created [a minimal reproduction](https://go.dev/play/p/Hxxa_xamCPO). Short version is that `{,*}x` works fine, but `{*,}x` does not.

I remember needing to have the project configured before build-opts worked, but I don't recall having a problem once it was configured. The build-opts hack is definitely showing its hackiness....

@kquick: in my experience, the problems with cabal install unnecessarily rebuilding dependencies have gone away with recent versions of cabal and cabal install. I used to see that behavior frequently,...

@kquick: I just took another look at this, and I think it would work fine if you had _installed_ the dependency instead of used add-source. Using add-source is equivalent to...

You did describe the use case for cabal-dev, and add-source accurately. The only difference is that after using add-source, you need to use cabal-dev install instead of cabal-dev build in...

We've made more progress on this issue. As of 4aa1b9102e8314de5596f54e3f95d5d36f020d79, we are using a trick lifted from leksah: Sniff the flags that cabal-install would pass to GHC and use those...

+1 We were just discussing how useful this would be.

Note that twitter-text-js will also have to account for supplementary code points in its validation of the 140 character limit (i.e. isInvalidTweet). I couldn't find length validation in twitter-text-java. Did...