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

Theory & advanced track #21

Open
17 tasks
turion opened this issue Mar 26, 2024 · 0 comments
Open
17 tasks

Theory & advanced track #21

turion opened this issue Mar 26, 2024 · 0 comments

Comments

@turion
Copy link
Owner

turion commented Mar 26, 2024

This track is to guide people into understanding more about how Rhine works internally, how to deal with more complicated type errors, and how to write your own clocks.

  • Show when/whether clock type parameters (like the interval in Millisecond) can be derived from a component, or vice versa. When it is not possible, recommend where to add type signature
  • LiftClock
  • Pure clocks
  • time domains
  • Rescale
  • Writing your own clock
  • Writing your own MonadSchedule
  • Complicated clock errors
    • After Make SN an Arrow rhine#261: Order of components (including a RB) is not the same as order of clocks in Rhine, this gives a weird error that HasClock cl '[] cannot be satisfied
    • When you write a ClSF without type signature, the clock type is not inferred. Revisit after Make ClSF a newtype rhine#268 though
  • Write your own backend to some library
  • Complicated Arrow syntax
  • ArrowPlus and ArrowChoice
  • Test your own rhines and develop them test-driven (rhine-quickcheck etc.)
@turion turion changed the title Theory track Theory & advanced track May 13, 2024
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

1 participant