-
When applying comparison operators (e.g., =, ) between two untyped objects, a check error is returned.
-
### Describe the issue
*TL;DR flow's input defaults should be correctly typed.*
---
Currently the flow's input `defaults` field is not typed - it is a simple `Object`. This can lead to unexpect…
-
Seems like lin 14 should get a UndefinedPropertyFetch similar to line 17 but doesnot: https://psalm.dev/r/169b4ab263
-
I think we added the typed connection builder with the intention of removing the untyped connection builder. Needs review.
-
For some reason, default parameters of procedures are not checked semantically (`typed`), which causes problems eg. when you want to get their type. Nim does not provide another mechanism of getting t…
-
-
Hello,
I've configured a gnmic to subscribe to interfaces counters, it works well and can be outputed as prometheus metrics.
```
# HELP nxos_openconfig_interfaces_interface_state_counters_in_di…
-
This issue can happen when there are too many nested templates or when the compiler can't efficiently manage deep template instantiations.
Current template: tests/asyncunit.nim
import unittest2, chro…
-
Currently, `*untyped` and `**untyped` can be used to accept any amount of any type of positional and keyword arguments. However, there's no way to accept a block of any type:
```rbs
def foo: () { (*…
-
**Issue**
Steep raises an error when it encounters the definition for a "proc with an untyped parameter"
Running Ruby 3.3.0 and Steep 1.7.1
**Steps to reproduce**
1. Define this proc in an…