Phobos-next Alternatives

Similar projects and alternatives to phobos-next based on common topics and language

Halide

43 5,700 9.5 C++ phobos-next VS Halide

a language for fast, portable data-parallel computation
anydsl

5 98 3.4 Shell phobos-next VS anydsl

Meta project to quickly build dependencies
WorkOS

workos.com sponsored

The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
verified-scheduling

1 30 0.9 Coq phobos-next VS verified-scheduling
toast

3 43 2.0 C++ phobos-next VS toast

Time Ordered Astrophysics Scalable Tools (by hpc4cmb)
exo

2 266 8.7 Python phobos-next VS exo

Exocompilation for productive programming of hardware accelerators (by exo-lang)
atl

1 55 3.2 Python phobos-next VS atl

A Tensor Language
phobos

1 1,169 9.5 D phobos-next VS phobos

The standard library of the D programming language (by dlang)
InfluxDB

www.influxdata.com sponsored

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.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better phobos-next alternative or higher similarity.

Suggest an alternative to phobos-next

phobos-next reviews and mentions

Posts with mentions or reviews of phobos-next. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-02-11.

A new programming language for high-performance computers
7 projects | news.ycombinator.com | 11 Feb 2022

The only language I know for sure to do it for you (as in you don't have to write the type) was Jai a while back (I'm told Blow removed that feature).
The only language I've actually done it in, is D. It's probably doable in many other nu-C languages these days, but D at very least can make it basically seamless as long as you do some try-and-break-shit testing to make sure nothing is relying on saving pointers when they shouldn't. This obviously constrains the definition of automatic ;)
I don't have my implementation to hand because it grew out of patch that failed due to aforementioned pointer-saving in code that I'm not paid enough to refactor (), but here's one someone else made https://github.com/nordlow/phobos-next/blob/master/src/nxt/s... there's another one in that repository too. I've never used those particular implementations but they're both by people I know so hopefully they're not too bad.
A more subtle thing, which I haven't used in anger, but would like to try at some point is to use programmer annotations (probably in the form of user defined attributes) to try and group things so things are stored such that temporal locality <=> spacial locality, but I've never bothered to actually do it.
There are some arrays of structs in an old bit of the D compiler that are roughly the size of a cacheline, and aren't accessed particularly uniformly. I profiled this and found that something like 75% of all LLC misses (hitting DRAM) were due to 2 particularly miserable lines... inside an O(n^2) algorithm.