Josh Triplett

We talked about this *at length* in today's @rust-lang/libs-api meeting. We very much want to add APIs for this. We'd ideally like to see the abstraction be slightly more portable,...

@rfcbot concern switch-to-option-1 I share @nikomatsakis's concern, and I would specifically like to go with option 1. This does not close the door on doing option 3 in the future,...

@rfcbot resolve switch-to-option-1 @rfcbot reviewed

We talked about this in today's @rust-lang/libs-api meeting, and we agreed to approve this.

If it's possible, I would love to see an implementation that can handle streaming data and still usefully use parallelism.

We talked about this in today's @rust-lang/libs-api meeting. We were in favor of `vec![...]` to define a vector always accepting any syntax that can be used for `[...]` to define...

I've read through the entirety of https://github.com/unicode-rs/unicode-width/issues/55 and https://github.com/unicode-rs/unicode-width/issues/64 , and as far as I can tell, I think the new behavior of unicode-width is *more correct* for tabled's purposes...

I've published a PR at https://github.com/zhiburt/tabled/pull/430 to use current unicode-width and improve width handling.

I think this issue can now be closed.

We re-discussed this in today's style meeting, and confirmed that we want to maintain the policy of not having ripple effects like this, as well as continuing to have the...