Skip to content
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

ZuriHac 2020 #40

Open
1 of 4 tasks
lehins opened this issue Jun 12, 2020 · 2 comments
Open
1 of 4 tasks

ZuriHac 2020 #40

lehins opened this issue Jun 12, 2020 · 2 comments

Comments

@lehins
Copy link
Owner

lehins commented Jun 12, 2020

This is the master ticket of all the ambitious goals for the ZuriHac 2020.

High level goal is that we need to rewrite HIP with massiv while getting rid of Repa and vector. Former is slower, while latter is redundant. Majority of the work already has been done in separate packages:

A lot of functionality for all these packages is currently embedded in HIP, but since it was my first attempt few years back it is far from optimal, so now we have newest and greatest to replace it with.

Feel free to submit tickets with any ideas or questions you might have. Or ask them on ZuriHac Discord channel

Guidlines

  • Important In order to start working on any particular issue, make sure to use massiv branch and submit all PRs with it as a target.
  • If you use stack then you are already set, if not then check out stack.yaml for custom pinned dependencies needed for current setup to build.

What can I work on?

I already ported a big portion of the library to massiv and Color. But there is still quite a bit of stuff that needs work. The idea is simple, look at current haddock on hackage and find parts that might be interesting to you. After you discover such function or topic then just checkout what is it current state. If it has been ported, try it out see if it works (maybe even write some haddokc, doctest, property/unit test or even a benchmark), if it is not ported yet, then open up a ticket just so no one else works on the same thing at the same time, and then try to reimplement it.

Feel freer to ask me any questions. One pointer is that there is work-in-progress fusion with rewrite rules implementation in place, you don't need to worry about it and you can simply ignore it, I'll handle it later on

Here is current list of tickets related to the hackathon:

@HanStolpo
Copy link
Contributor

I am doing this one next - #44

@HanStolpo
Copy link
Contributor

I am doing this one next #46

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants