-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
In Ecstasy, there is always one module imported (the core ecstasy module itself), and we decided to explicitly select by hand the names to have in scope. Those names are listed in the implicit.x resource file, and include obvious things like Boolean, True, False, String, Int, and so on.
Hmm, so I still feel that C3's imports actually are binding to a specific implementation like other imports (Java/C/python/etc). I think a language would need to embed dependency injection concepts deep into its veins to avoid this. You'd need a way for implementation files to specify that they depend on something with a certain name and a certain interface but not to name the specific implementation. Then a separate parallel module system (more like a Guice (dep injection framework) module than the modules in C3) would indicate the specific implementation that happens to be desired this run of the program. This is the inherent modularity that I'm looking to implement in Claro. There's some prototyping of this idea in the example programs at https://github.com/JasonSteving99/claro-lang/blob/main/src/java/com/claro/claro_programs/modules.claro
Related posts
-
Stirling PDF: Self-hosted, web-based PDF manipulation tool
-
Ask HN: Best stack for building a desktop app?
-
Open VSX – Extensions for VS Code Compatible Editors
-
LLM Based Input Space Partitioning Testing for Library APIs (a.k.a. Bogus CVEs)
-
Intel submitted OpenJDK PRs for supporting new 64 bit general purpose registers