Revision 39dc9b7c915401697cd07d4ff6757cc383899bfe authored by Anish Tondwalkar on 30 April 2019, 17:16:17 UTC, committed by Anish Tondwalkar on 30 April 2019, 17:16:17 UTC
This implementation works for non-implicits, but when you have implicit paramters, polymorphism, and ANF, the bidirectional approach doesn't quite work. You end up with something like ```haskell let anf0 :: SST Int Int Int = (>>) @Int @Int @Int in get >> get ``` The problem is that the implicit information simply travels up, not down! Seems the solution is to either not use bidi, or make fresh and <: allocate implicit paramters and solve for them.
1 parent 62681dd
LICENSE
Copyright (c) 2016 Ranjit Jhala
Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:
The above copyright notice and this permission notice shall be included
in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Computing file changes ...
