Dave Raffensperger

I'd like to avoid making BigInt / jsbi a requirement for users, since it would add weight to the JS bundles that get shipped to the browser. That said, you...

There is also the [long.js](https://github.com/dcodeIO/long.js) library, which is likely lighter weight than jsbi since it only needs 64-bit support. Again, something I'd recommend we look at down the road.

What if we have a single interface, and make the type for it accept something like `number|bigint`? Then in our implementation, we make sure that the `bigint` dependency is pluggable...

The way the OpenCensus service's grpc-gateway works is that you can give a `value` field and a string for the number, something like `{value: {int64Value: "string of the 64-bit number"}}`....

I would agree with the value of creating nested child spans. If there are multiple interesting operations with sub-operations within a given request, and they are executing in parallel, then...

We may be able to make this less of a breaking change by introducing new field names for `Span` for the high resolution start/end times but keep `start` and `end`...

Thanks for the contribution BTW! I have been thinking about this type of functionality and see https://github.com/census-instrumentation/opencensus-node/issues/105 for more

I was wondering about that myself too. From a purely Node.js perspective, I think merging the two makes total sense. For the `opencensus-web` project though, what I'm hoping to do...

Whether or not we end up doing the work to separate out a `core-types` package, I think at a minimum it would be useful to make sure that there are...

So the core issue is that the C compiler can't find the lp_solve.h file. It's fine to have the lpsolve IDE installed, but I think you'll also need the development...