tree 68e323832a614bdbba8047b00bf916e6508a5061
parent 785e6b4b56f61d2d22130400b8ef40c66aeae9c4
author Devin Jeanpierre <jeanpierreda@google.com> 1674519217 -0800
committer Copybara-Service <copybara-worker@google.com> 1674519251 -0800

Move remaining runtime libraries to `crubit/support`.

This is not "obviously" correct: the current contents of crubit/support are only the runtime libraries that are present in generated code. But I don't think that's an important distinction -- rather, I think it's valuable to have all user-facing libraries in the same place.

(I would be "support"-ive of basically any directory scheme that puts them together. An alternative design, for example, is to unwrap `support/*` into `third_party/crubit`, so that people depend on `crubit:foo` instead of `crubit/support:foo`. Alternatively, we could rename `support` to `public` or `lib`, but keep it as is. Or, finally, we can just keep it as is.)

For now, moving into `support` makes it easier to find the user-facing libraries.

PiperOrigin-RevId: 504107815