leostera / leostera/minttea

Type error into examples

Open
#32 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug good first issue help wanted
Dominant language
OCaml
Stars
472
Forks
32
PR merge metrics
No merged PRs in 30d

Description

Hello,

Just my first step with Minttea. Very good idea to be inspired by Elm and powered by OCaml.

dune --version 
3.13.1
ocaml --version
The OCaml toplevel, version 5.1.1
➜  progress git:(main) ✗ dune build
Entering directory '/Users/nicolas.muller/projects/minttea/minttea'
File "minttea/renderer.ml", line 112, characters 36-54:
112 |     Riot.Timer.send_interval ~every:(fps_to_float fps) (self ()) Tick
                                          ^^^^^^^^^^^^^^^^^^
Error: This expression has type int64 but an expression was expected of type
         float
File "minttea/program.ml", line 47, characters 54-59:
47 |       let _ = Timer.send_after (self ()) (Timer ref) ~after |> Result.get_ok in
                                                           ^^^^^
Error: This expression has type int64 but an expression was expected of type
         `float`

Thanks a lot,
Nicolas

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running dune build with the reported OCaml and Dune versions, then inspect minttea/renderer.ml around line 112 and minttea/program.ml around line 47. Determine why the reported timer calls receive int64 values where float is expected; done means the examples build without these type errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
ocaml
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.