create sounds like it always returns a new object, which it doesn't do anymore then.

create sounds like it always returns a new object, which it doesn't do anymore then.

Yes, I suppose you're right. My initial thinking was create would better indicate the method should be called rather than reusing a prior Suspension object by the consumer (which may have been associated with a different fiber). However, create certainly doesn't make this obvious and will need to be documented anyway. get likely does make more sense then. I'm fine if you want to change that now as part of this PR.

getX also gives the assumption that it always returns the same suspension.

DriverInterface::suspension(): SuspensionInterface - return, or create suspension for the current fiber

It does return the same instance, per fiber. It's similar to a ThreadLocal in Java.

yea, but I'm talking generally ( as between different fibers ), maybe DriverInterface::currentSuspension()?

@trowski @WyriHaximus Renamed and added a documentation comment that the driver must always return the same instance for each fiber.

+1 for keeping the old method and deprecating it during 0.2.x.

I've added EventLoop::createSuspension again to allow for a smoother transition from 0.1 to 0.2, so libraries can mostly require ^0.1 || ^0.2 instead of directly jumping to ^0.2.