Summary:
See the test for a concrete example.
We have a scenario where both a library, and a service using that library, are using fiber. Managing a separate similar-sized thread and event-base pool costs us complexity and performance. So this seems like a legit need.

The overall solution is to hash the Options struct.
But because that has some cost, I made it optional, by introducing a new FrozenOptions struct.

Reviewed By: andriigrynenko

Differential Revision: D15305274

fbshipit-source-id: 5c53d8c4ed321ae88089c64de41af8229f877d36