Re: How does GHC handle TcPluginContradiction?

I also just found issue #22 in Adam's uom github repository; it seems related. """ The plugin is correctly reporting the constraint Base "s" ~~ Base "m" ^: 2 as insoluble (note the use of ~~, which is a type family provided by uom-plugin that is a pseudo-synonym of ~). However, it turns out that

Re: How does GHC handle TcPluginContradiction?

Yes, thanks! I agree with you. I just realized on my dog walk that, according to https://ghc.haskell.org/trac/ghc/wiki/Plugins/TypeChecker, "If the plugin finds a contradiction amongst the givens, it should return TcPluginContradiction containing the contradictory constraints. These will turn

How does GHC handle TcPluginContradiction?

My TC plugin is identifying a contradiction, but that is not preventing the module from type checking, nor does GHC even raising a warning (with -Wall). This is not the behavior I was expecting. How confused am I? I've distilled the behavior that's confusing me down to the following example >

Job opening: compiling to categories

I have a job opening to work closely with me (at Target Digital) on the GHC plugin described in the paper *Compiling to Categories* as well as on applications, including machine learning. I’m especially looking for someone used to working inside of