nim-chronos

nim-chronos copied to clipboard

Why does this usage of asyncSpawn and ThreadSignalPtr leak memory?

4

Heyho, still trying to write my multithreading library and ensuring correctness with address sanitizer. I've been running into memory leak issues of around 20KB with the way I have set...

PhilippMDoerner

Following example is impossible to compile ```nim import chronos func foo*[T](future: Future[T].Raising([])): bool = false when isMainModule: let resFut = Future[void].Raising([CancelledError]).init() echo foo(resFut) ``` It will generate an error: ```...

cheatfate

Completing `Futures` in refc may have unexpected behavior

1

I've recently bumped into [an issue that affects how `sink` parameters behave in refc](https://github.com/nim-lang/Nim/issues/23354) and which can have adverse effects on Chronos' (V4) futures: `sink` parameters can end up being...

gmega

`SIGSEGV` in `asyncTest`-derived scenario (also, in `asyncTest`)

5

```nim import chronos # only depends on asyncloop's transitive closure proc t(): Future[int] {.async: (raw: true, raises: [ValueError]).} = var retFuture = newFuture[int]("") retFuture.fail(newException(ValueError, "")) return retFuture proc m(transp: int):...

tersec