this post was submitted on 31 Jan 2025
22 points (100.0% liked)

Programming

18040 readers
62 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]



founded 2 years ago
MODERATORS
 

I'm a D developer who recently got into the whole WASM thing with it using betterC (I do plan to write my own very minimalistic runtime to allow me using classes yet again), and currently I'm looking into enhancing the language's support of WASM in one way or another, especially when it comes to two "exotic" types of WASM, externref and funcref (there's also exnref, but it's just before finalization, so I'm waiting a bit with that one).

Me and others also programming in D have experimented with LDC (D compiler with LLVM backend) attributes since those types supposed to be address space 10 and 20 pointers, but I don't know whether the issue is that LDC doesn't handle type/pointer attributes the way we expected it to thus ending up generating i32 instead, or that I specifically need to emit the types for the LLVM backend.

top 1 comments
sorted by: hot top controversial new old
[–] [email protected] 1 points 3 days ago

So far it seems the issue could be solved by LDC's magic attribute/pragma system, except it isn't hooked up to the address space system.