Skip to content

As part of incremental type checking, when filtering out potentially unwanted parser errors, don't ignore the multiple definitions type error #2931

As part of incremental type checking, when filtering out potentially unwanted parser errors, don't ignore the multiple definitions type error

As part of incremental type checking, when filtering out potentially unwanted parser errors, don't ignore the multiple definitions type error #2931

Triggered via pull request April 29, 2025 12:39
Status Success
Total duration 10m 23s
Artifacts 6

ci.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Artifacts

Produced during runtime
Name Size Digest
darwin
4.73 MB
sha256:bd4db61b4939d04cca4f906d2bb96ca35d78ce30185c70efa2db8b620ff824a0
darwinarm64
5.27 MB
sha256:4ed7a415be6db80c23f1d0f19968781c08366b5de6d776e4f2a6632f25e3852f
linux
4.75 MB
sha256:1d2d1e202854195d5ce0a5f926d8cb9567c50ffb2db44865fd419e167a4614bb
linuxarm64
5.37 MB
sha256:524a939e6fa28406a18e6222a68413696ed88fe17ac2683adadf05ff57926ecd
rescript-vscode-7406e82.vsix
15.4 MB
sha256:db1168bccbdd1c31fe096161e15c99f45824eb171fffb3813c7e1bb5eda44075
win32
8.14 MB
sha256:d57748c3ac5d1c40763578f4246dc145fa12f774f609297b7b10aa02700ac9a8