+1

test/cram/e820.t/bad/dune-project

reviewed

··· 1 1 + (lang dune 3.21)

+5

test/cram/e820.t/bad/foo/test/interop/oracle/test.ml

reviewed

··· 1 1 + let () = 2 2 + let ic = open_in "traces/sample.csv" in 3 3 + let line = input_line ic in 4 4 + let _fields = String.split_on_char ',' line in 5 5 + close_in ic

+1

test/cram/e820.t/good/dune-project

reviewed

··· 1 1 + (lang dune 3.21)

+4

test/cram/e820.t/good/foo/test/interop/oracle/test.ml

reviewed

··· 1 1 + let () = 2 2 + match Csv.decode_file "traces/sample.csv" Csv.Row.codec with 3 3 + | Ok _rows -> () 4 4 + | Error _ -> ()

+47

test/cram/e820.t/run.t

reviewed

··· 1 1 + Test bad example - test.ml hand-rolls CSV parsing: 2 2 + $ merlint -B -r E820 bad/ 3 3 + Running merlint analysis... 4 4 + 5 5 + Analyzing 0 files 6 6 + 7 7 + ✓ Code Quality (0 total issues) 8 8 + ✓ Code Style (0 total issues) 9 9 + ✓ Naming Conventions (0 total issues) 10 10 + ✓ Documentation (0 total issues) 11 11 + ✓ Project Structure (0 total issues) 12 12 + ✓ Test Quality (0 total issues) 13 13 + ✗ Interop Testing (1 total issues) 14 14 + [E820] Hand-rolled CSV parsing (1 issue) 15 15 + Use csv (Csv.decode_file with a Csv.Row codec) for CSV trace parsing. Never 16 16 + hand-roll CSV readers with open_in/input_line/split_on_char. 17 17 + - (global) Interop test bad/foo/test/interop/oracle/test.ml hand-rolls CSV parsing instead of csv 18 18 + ✓ Code Generation (0 total issues) 19 19 + 20 20 + ╭─────────────────┬───────────────────────────────╮ 21 21 + │ Category │ Issues │ 22 22 + ├─────────────────┼───────────────────────────────┤ 23 23 + │ Interop Testing │ 1 (1 hand-rolled csv parsing) │ 24 24 + ╰─────────────────┴───────────────────────────────╯ 25 25 + 26 26 + 27 27 + Summary: ✗ 1 total issue (applied 1 rule) 28 28 + ✗ Some checks failed. See details above. 29 29 + [1] 30 30 + 31 31 + Test good example - test.ml uses csv library: 32 32 + $ merlint -B -r E820 good/ 33 33 + Running merlint analysis... 34 34 + 35 35 + Analyzing 0 files 36 36 + 37 37 + ✓ Code Quality (0 total issues) 38 38 + ✓ Code Style (0 total issues) 39 39 + ✓ Naming Conventions (0 total issues) 40 40 + ✓ Documentation (0 total issues) 41 41 + ✓ Project Structure (0 total issues) 42 42 + ✓ Test Quality (0 total issues) 43 43 + ✓ Interop Testing (0 total issues) 44 44 + ✓ Code Generation (0 total issues) 45 45 + 46 46 + Summary: ✓ 0 total issues (applied 1 rule) 47 47 + ✓ All checks passed!