-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tracking issue for missing features #77
Comments
Hey @Nadrieril is there any low hanging fruit where I could get started here? I'm new to Rust, but familiar with Dhall and have contributed to the language and Haskell implementation. Willing to get my hands dirty here 🙇 |
Hey @FintanH ! Thanks for your interest in this project ! I'm glad you're willing to get your hands dirty because this project is quite a mess ^^ |
Ya, I can give it a shot! :) |
Yay ! Could you open an issue about that feature ? Then over there you can bombard me with questions about the structure of the project, where the different bits are, how |
@basile-henry: if you're interested too, you're welcome to try recursive record merge for example. Just open an issue too and ask away ! |
@Nadrieril I might have a go at recursive record merge this weekend if no one has started working on that by then! 😄 |
You can link the issue to the checklist if you want now :) #86 |
I've created an issue for |
@FintanH I did start working on it but I didn't get very far. The codebase has changed quite a bit since last time I looked at it and I was struggling to find all the pieces I needed. |
@Nadrieril I'm feeling some momentum after putting up those PRs for typechecking. What would make the most sense for working on next? 😁 |
@FintanH :D |
I was thinking import would be next too. I'll do up some tickets and do some digging! |
There's a new feature to implement: projection by expression (#94) ! There's everything from parsing to typechecking left to implement, if anyone's interested |
@basile-henry @FintanH I've given both of you merge rights to this repo, so that you can merge your own PRs yourselves :). Here is what I propose: you can merge a PR yourself after I've approved it, or otherwise if I haven't approved or disapproved for 7 days you can go ahead and merge it (like what's done in |
Ya that sounds great. Thanks! |
I wrote one or two good first issues if anyone is interested :) |
Now that most features are done, I'm closing this in favor of labeled issues https://github.com/Nadrieril/dhall-rust/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3Astandard-compliance |
Dhall spec
toMap
toMap
keyword #96as Location
Implement a bunch of missing features #139Integer/show
Natural/show
Double/show
Natural/toInteger
#
, akaListAppend
Text/show
//\\
, akaCombineTypes
andRecursiveRecordTypeMerge
Implement Type Check for //\\ #91/\
, akaCombine
andRecursiveRecordMerge
Implement Type Check for/\
#89//
, akaPrefer
andRightBiasedRecordMerge
Implement Type Check for//
#86record.{ x, y, z }
)union.x
)toMap
toMap
keyword #96Integer/show
Natural/show
Double/show
Natural/toInteger
#
, akaListAppend
Text/show
//\\
, akaCombineTypes
andRecursiveRecordTypeMerge
/\
, akaCombine
andRecursiveRecordMerge
//
, akaPrefer
andRightBiasedRecordMerge
record.{ x, y, z }
)union.x
)toMap
toMap
keyword #96Pretty error messages
Error
typePublic API
settle lifetime behaviour in expr lifecycleexpression lifecycleThe text was updated successfully, but these errors were encountered: