Skip to content

Fix handling of double dashes -- in crystal eval command #15376

Fix handling of double dashes -- in crystal eval command

Fix handling of double dashes -- in crystal eval command #15376

Triggered via pull request February 14, 2025 14:28
@kojix2kojix2
synchronize #15477
kojix2:eval
Status Failure
Total duration 3m 25s
Artifacts

win.yml

on: pull_request
x86_64-windows-libs
1m 44s
x86_64-windows-libs
x86_64-windows-dlls
1m 20s
x86_64-windows-dlls
x86_64-windows-llvm-libs
20s
x86_64-windows-llvm-libs
x86_64-windows-llvm-dlls
21s
x86_64-windows-llvm-dlls
x86_64-windows-release  /  build
1m 3s
x86_64-windows-release / build
x86_64-windows-test
0s
x86_64-windows-test
x86_64-windows-test-interpreter
0s
x86_64-windows-test-interpreter
x86_64-windows-installer
0s
x86_64-windows-installer
Fit to window
Zoom out
Zoom in

Annotations

2 errors
x86_64-windows-release / build: src/compiler/crystal/command/eval.cr#L23
expected argument #2 to 'Crystal::Compiler::Source.new' to be String, not (String | Nil)
x86_64-windows-release / build
Process completed with exit code 1.