Does it make sense for copilot-core to offer extractProp?
#669
ivanperez-keera
started this conversation in
General
Replies: 2 comments 4 replies
|
For context, this was introduced in #596. I wasn't quite sure how best to handle this when authoring #596. The |
1 reply
|
For context also, here's the one in |
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
copilot-corepublishes a functionextractPropthat is barely used across Copilot, and is considered to lose information so there's a big disclaimer attached to it:https://hackage-content.haskell.org/package/copilot-core-4.5.1/docs/Copilot-Core-Spec.html#v:extractProp
Does it make sense for the library to publish that function? Should it be local to where it is used?
(Note that
copilot-languagehas a similar function that operates on higher-level constructs.)All reactions