Skip to content

Conversation

@diegomrsantos
Copy link
Contributor

@diegomrsantos diegomrsantos commented Aug 29, 2024

It makes it possible to not use InternalRaisesFuture in procs like https://github.com/vacp2p/nim-libp2p/pull/1175/files.

@diegomrsantos diegomrsantos force-pushed the make-SomeFuture-public branch from d6a1f8a to ef93a15 Compare August 29, 2024 20:24
## Error raised when trying access the error of a completed Future

SomeFuture = Future|InternalRaisesFuture
SomeFuture* = Future|InternalRaisesFuture
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this type is deliberately private because the whole idea of how this is implemented might change soonish - for now, it's better to use InternalRaisesFuture directly in code that needs it which will make it easy to find, once a stable future type is created.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants