Create guidelines for integration Beman libraries into Compiler Explorer

[neatudarius]

Create guidelines for integration Beman libraries into Compiler Explorer

• Add actual guidelines
  • Header-only library
  • Library with actual binaries
• Examples with beman.optional26 and beman.iterator_interface

[neatudarius]

Related to naming conventions, the Beman Standard uses beman.<short_name, which is kept.

But inside the CE config, we need to be aware of CE internal renaming. At Beman weekly seek we decided to incorporate such guidelines into one Beman docs:

When integrating into Compiler Explorer, any beman.<short_name> Beman library name should be converted to beman_<short_name> for filling in the keys in YAML/configs inside the Compiler Explorer infrastructure (no actual change inside the Beman org). The display name from CE UI can be still set to beman.<short_name>, via libs.beman_.name = beman.<short_name>.

[wusatosi]

Is there a chance that we will consider hosting our own version of compiler explorer?

I can see a lot of benefit with this, e.g. we can see codegen of a library based on main/ when a full release is not ready yet.

Many features may dependent on forks of llvm that implements specific feature, would be eaiser to check on those platforms as well.

[neatudarius]

Is there a chance that we will consider hosting our own version of compiler explorer?

I can see a lot of benefit with this, e.g. we can see codegen of a library based on main/ when a full release is not ready yet.

Many features may dependent on forks of llvm that implements specific feature, would be eaiser to check on those platforms as well.

I don't think custom infrastructure is something we want to prioritize in the next months for components which are good enough. At this point, I would concentrate our efforts for 1) guidelines to integrate into CE and 2) actually integrate all Beman libraries in CE.

I think your suggestion is for a long term approach.

[neatudarius]

Changes under review in #109