Go's for loops can only iterate over builtin types: slices, maps, channels, etc. You can't produce a custom type that is to be iterated over.
4,353 karma · joined June 19, 2011
Go's for loops can only iterate over builtin types: slices, maps, channels, etc. You can't produce a custom type that is to be iterated over.
Go's compiler is just particularly naive.
Just like with monomorphisation, Go just stubbornly rejects all PL research younger than 40.
The US democrats exist to divert any worker resistance into channels they can then sabotage. In many ways they're more right wing than the US Republicans, especially when it comes to foreign policy.
PII is a similar but different US concept.
In practice, games (usually through engines) overwhelmingly target the native graphics APIs. D3D12 on Windows and Xbox, GNM on PS5, Metal on iOS/macOS/tvOS, NVN on Switch, etc. In practice it doesn't matter much.
MoltenVK is not as good as DXVK right now, sure. That still has nothing to do with either Apple or Microsoft. They both offer exactly as much support.
The chips in MacBook Pros aren't the bulk of the cost. I think it's unlikely Apple would make a console, but still possible. They have all of the necessary ingredients already vertically integrated.
I am a game developer, btw.
Other car functions use computers for very different reasons. The most successful is injection timing, which does significantly improve performance. It's why we have extremely efficient small diesel engines and reasonably powerful 1L petrol engines.
Metal has sort of been ported to other platforms, WebGPU is almost a subset of it (albeit somewhat higher level). There's even wgpu to use it outside of a browser.
It's possible Apple might make an M1 Apple TV with a decent GPU. Like the Macbook Air, it's likely it'd be cheaper to manufacture than competitors with similar performance. I suppose we'll see.
It’s a reasonable ORM, but doesn’t compare to SQLAlchemy.