The D Programming Language - Digitalmars-d

March 2024 Archives by date

• Messages sorted by: [ thread ] [ subject ] [ author ]
• More info on this list...

Starting: Fri Mar 1 00:02:44 UTC 2024
Ending: Sun Mar 31 15:52:26 UTC 2024
Messages: 394

• How to make D resolve C++ symbols by mangling symbols with the Itanium ABI on Windows   Carl Sturtivant
• What ever happened to move semantics?   electricface
• How to make D resolve C++ symbols by mangling symbols with the Itanium ABI on Windows   Carl Sturtivant
• How to make D resolve C++ symbols by mangling symbols with the Itanium ABI on Windows   thumbgun
• ImportC now supports function-like macros   Dakota
• How to make D resolve C++ symbols by mangling symbols with the Itanium ABI on Windows   thumbgun
• ImportC now supports function-like macros   ryuukk_
• ImportC now supports function-like macros   Dakota
• How to make D resolve C++ symbols by mangling symbols with the Itanium ABI on Windows   Mathias LANG
• What ever happened to move semantics?   Don Allen
• How to make D resolve C++ symbols by mangling symbols with the Itanium ABI on Windows   Carl Sturtivant
• Beeflang garbage seeker/collector   H. S. Teoh
• ImportC now supports function-like macros   Walter Bright
• Refactoring Code   Walter Bright
• Refactoring Code   claptrap
• Refactoring Code   Paul Backus
• ImportC now supports function-like macros   Jonathan M Davis
• Refactoring Code   Max Samukha
• Refactoring Code   Walter Bright
• Refactoring Code   Max Samukha
• Refactoring Code   ryuukk_
• ImportC now supports function-like macros   Richard (Rikki) Andrew Cattermole
• A proposal: Sumtypes   IchorDev
• ImportC now supports function-like macros   Walter Bright
• ImportC now supports function-like macros   Dakota
• Generic memory allocation in D   Walter Bright
• Generic memory allocation in D   Dom DiSc
• Generic memory allocation in D   Walter Bright
• Generic memory allocation in D   Hipreme
• Generic memory allocation in D   Dom DiSc
• Generic memory allocation in D   Dennis
• Generic memory allocation in D   Richard (Rikki) Andrew Cattermole
• Generic memory allocation in D   Daniel N
• Generic memory allocation in D   Paul Backus
• Range Redesign: Empty Ranges   Jonathan M Davis
• Range Redesign: Empty Ranges   Sebastiaan Koppe
• Generic memory allocation in D   Meta
• ImportC: Overriding standard search paths for C includes   kdevel
• Refactoring Code   kdevel
• Generic memory allocation in D   kdevel
• Range Redesign: Empty Ranges   Jonathan M Davis
• Generic memory allocation in D   Walter Bright
• Generic memory allocation in D   Walter Bright
• Generic memory allocation in D   Walter Bright
• Generic memory allocation in D   Walter Bright
• Generic memory allocation in D   Richard (Rikki) Andrew Cattermole
• Generic memory allocation in D   Ogi
• Generic memory allocation in D   kdevel
• Generic memory allocation in D   Dom DiSc
• Frontier Airlines Seat Selection |+1-800-315-2771| Policy. Rules & Guidelines   flight villa
• Generic memory allocation in D   Adam Wilson
• Generic memory allocation in D   ShadoLight
• Generic memory allocation in D   Guillaume Piolat
• Range Redesign: Empty Ranges   Dom DiSc
• Generic memory allocation in D   Richard (Rikki) Andrew Cattermole
• Range Redesign: Empty Ranges   Alexandru Ermicioi
• Generic memory allocation in D   Walter Bright
• Range Redesign: Empty Ranges   Adam Wilson
• Range Redesign: Empty Ranges   H. S. Teoh
• Refactoring Code   Basile B.
• Range Redesign: Empty Ranges   Adam Wilson
• Range Redesign: Empty Ranges   Arafel
• Google's take on memory safety   RazvanN
• Google's take on memory safety   Sergey
• run.dlang.io - is still broken: "export gist" and "shorten" buttons are not working.   BoQsc
• [SAoC 2023] Replace DRuntime Hooks with Templates Weekly Update #10   Richard
• static switch over is expression cases?   Richard
• Refactoring Code   ryuukk_
• Google's take on memory safety   RazvanN
• Range Redesign: Empty Ranges   Alexandru Ermicioi
• Range Redesign: Empty Ranges   Dom DiSc
• Google's take on memory safety   Sergey
• Range Redesign: Empty Ranges   Arafel
• Range Redesign: Empty Ranges   Atila Neves
• Range Redesign: Empty Ranges   Ogi
• Range Redesign: Empty Ranges   Paul Backus
• Range Redesign: Empty Ranges   Paul Backus
• Range Redesign: Empty Ranges   Steven Schveighoffer
• Google's take on memory safety   Richard (Rikki) Andrew Cattermole
• Google's take on memory safety   H. S. Teoh
• Range Redesign: Empty Ranges   H. S. Teoh
• Range Redesign: Empty Ranges   Paul Backus
• Range Redesign: Empty Ranges   Paul Backus
• Range Redesign: Empty Ranges   Meta
• Range Redesign: Empty Ranges   H. S. Teoh
• Range Redesign: Empty Ranges   Richard (Rikki) Andrew Cattermole
• Range Redesign: Empty Ranges   H. S. Teoh
• Google's take on memory safety   M. M.
• Google's take on memory safety   M. M.
• Range Redesign: Empty Ranges   Jonathan M Davis
• Google's take on memory safety   H. S. Teoh
• Range Redesign: Empty Ranges   Jonathan M Davis
• Range Redesign: Empty Ranges   Jonathan M Davis
• Range Redesign: Empty Ranges   H. S. Teoh
• Range Redesign: Empty Ranges   Meta
• Range Redesign: Empty Ranges   Dukc
• Google's take on memory safety   Sergey
• Range Redesign: Empty Ranges   Jonathan M Davis
• Range Redesign: Empty Ranges   Jonathan M Davis
• Range Redesign: Empty Ranges   H. S. Teoh
• Google's take on memory safety   matheus
• Google's take on memory safety   H. S. Teoh
• Range Redesign: Empty Ranges   Meta
• Range Redesign: Empty Ranges   Dukc
• Range Redesign: Empty Ranges   Jonathan M Davis
• Google's take on memory safety   aberba
• Range Redesign: Empty Ranges   Atila Neves
• Range Redesign: Empty Ranges   Jonathan M Davis
• Google's take on memory safety   Dom DiSc
• A proposal: Sumtypes   cc
• Range Redesign: Empty Ranges   Ogi
• Google's take on memory safety   Monkyyy
• Google's take on memory safety   DrDread
• Range Redesign: Empty Ranges   Steven Schveighoffer
• Range Redesign: Empty Ranges   Steven Schveighoffer
• A proposal: Sumtypes   Richard (Rikki) Andrew Cattermole
• Range Redesign: Empty Ranges   H. S. Teoh
• Range Redesign: Empty Ranges   Paul Backus
• Google's take on memory safety   Walter Bright
• Google's take on memory safety   Walter Bright
• Google's take on memory safety   Monkyyy
• Google's take on memory safety   Paulo Pinto
• Google's take on memory safety   Dukc
• Google's take on memory safety   Marconi
• Generic memory allocation in D   cc
• Google's take on memory safety   monkyyy
• Google's take on memory safety   monkyyy
• Google's take on memory safety   Paulo Pinto
• Google's take on memory safety   Paulo Pinto
• Google's take on memory safety   H. S. Teoh
• Google's take on memory safety   monkyyy
• Generic memory allocation in D   Walter Bright
• Google's take on memory safety   Gregor Mückl
• Generic memory allocation in D   Daniel N
• Google's take on memory safety   Paolo Invernizzi
• Google's take on memory safety   Paulo Pinto
• Generic memory allocation in D   Richard (Rikki) Andrew Cattermole
• Generic memory allocation in D   claptrap
• Google's take on memory safety   Walter Bright
• Google's take on memory safety   Lance Bachmeier
• Google's take on memory safety   Walter Bright
• Google's take on memory safety   Emmanuel Danso Nyarko
• DMD backend generation future with the new AI race processor   Hipreme
• DMD backend generation future with the new AI race processor   Walter Bright
• Google's take on memory safety   Walter Bright
• DMD backend generation future with the new AI race processor   Richard (Rikki) Andrew Cattermole
• DMD backend generation future with the new AI race processor   Brad Roberts
• Google's take on memory safety   Carl Sturtivant
• DMD backend generation future with the new AI race processor   Richard (Rikki) Andrew Cattermole
• Memory safe in D   Alex
• Memory safe in D   Richard (Rikki) Andrew Cattermole
• Memory safe in D   Sergey
• Google's take on memory safety   Martyn
• Google's take on memory safety   Martyn
• Memory safe in D   Alex
• Memory safe in D   Alex
• Memory safe in D   Richard (Rikki) Andrew Cattermole
• Memory safe in D   Sergey
• Memory safe in D   Alex
• Memory safe in D   Alex
• Memory safe in D   Richard (Rikki) Andrew Cattermole
• Memory safe in D   Nick Treleaven
• Memory safe in D   Alex
• Memory safe in D   Richard (Rikki) Andrew Cattermole
• Memory safe in D   Alex
• Memory safe in D   Alex
• Memory safe in D   Ogi
• Memory safe in D   bachmeier
• Memory safe in D   Richard (Rikki) Andrew Cattermole
• Memory safe in D   Steven Schveighoffer
• Memory safe in D   Alex
• DMD backend generation future with the new AI race processor   Ben Jones
• Memory safe in D   bachmeier
• Memory safe in D   Richard (Rikki) Andrew Cattermole
• Memory safe in D   Walter Bright
• Memory safe in D   Walter Bright
• DMD backend generation future with the new AI race processor   electricface
• Memory safe in D   Walter Bright
• Memory safe in D   Walter Bright
• Memory safe in D   Walter Bright
• Memory safe in D   Walter Bright
• DMD backend generation future with the new AI race processor   Walter Bright
• DMD backend generation future with the new AI race processor   Walter Bright
• DMD backend generation future with the new AI race processor   Walter Bright
• DMD backend generation future with the new AI race processor   Walter Bright
• Memory safe in D   Walter Bright
• DMD backend generation future with the new AI race processor   Richard (Rikki) Andrew Cattermole
• DMD backend generation future with the new AI race processor   Walter Bright
• DMD backend generation future with the new AI race processor   Richard (Rikki) Andrew Cattermole
• Memory safe in D   Alex
• Google's take on memory safety   dweldon
• Google's take on memory safety   Martyn
• Memory safe in D   Steven Schveighoffer
• Memory safe in D   An Pham
• Memory safe in D   Lance Bachmeier
• Memory safe in D   Walter Bright
• Memory safe in D   Walter Bright
• Memory safe in D   Walter Bright
• Memory safe in D   Walter Bright
• Memory safe in D   Lance Bachmeier
• Memory safe in D   Steven Schveighoffer
• Memory safe in D   Walter Bright
• Memory safe in D   Alex
• Memory safe in D   H. S. Teoh
• Memory safe in D   cc
• Memory safe in D   Walter Bright
• Memory safe in D   Walter Bright
• Memory safe in D   Walter Bright
• Memory safe in D   Walter Bright
• Memory safe in D   Ogi
• Memory safe in D   Alex
• Memory safe in D   Alex
• Memory safe in D   Alex
• Memory safe in D   Richard (Rikki) Andrew Cattermole
• Memory safe in D   Petar
• Memory safe in D   Petar
• forum.dlang.org as a flashlight app   Ferhat Kurtulmuş
• Memory safe in D   Steven Schveighoffer
• Google's take on memory safety   Germán Diago
• Google's take on memory safety   bachmeier
• Memory safe in D   Alex
• Memory safe in D   Steven Schveighoffer
• Memory safe in D   Alex
• Google's take on memory safety   jmh530
• Memory safe in D   Alex
• Google's take on memory safety   bachmeier
• Memory safe in D   Jonathan M Davis
• Memory safe in D   cc
• Memory safe in D   Steven Schveighoffer
• What is zopisign 7.5 mg?   olivia pitter
• Memory safe in D   Alex
• Memory safe in D   Alex
• Memory safe in D   Alex
• forum.dlang.org as a flashlight app   Ogi
• Separate dynamic object arrays for multiple instances of overlying object   Jonathan
• Separate dynamic object arrays for multiple instances of overlying object   Richard (Rikki) Andrew Cattermole
• Separate dynamic object arrays for multiple instances of overlying object   Mike Parker
• Separate dynamic object arrays for multiple instances of overlying object   Jonathan
• Separate dynamic object arrays for multiple instances of overlying object   Jonathan
• Separate dynamic object arrays for multiple instances of overlying object   Basile B.
• Separate dynamic object arrays for multiple instances of overlying object   An Pham
• Separate dynamic object arrays for multiple instances of overlying object   Jonathan
• Separate dynamic object arrays for multiple instances of overlying object   Matheus
• Memory safe in D   Nick Treleaven
• forum.dlang.org as a flashlight app   Meta
• forum.dlang.org as a flashlight app   Basile B.
• Separate dynamic object arrays for multiple instances of overlying object   Timon Gehr
• Separate dynamic object arrays for multiple instances of overlying object   matheus
• Google's take on memory safety   harakim
• Memory safe in D   Don Allen
• Google's take on memory safety   Lance Bachmeier
• Spec: can a class method change the type of the object (vtable) ?   Johan
• Voldemort toHexString Compile Error   Salih Dincer
• Voldemort toHexString Compile Error   Richard (Rikki) Andrew Cattermole
• Voldemort toHexString Compile Error   kdevel
• Voldemort toHexString Compile Error   Richard (Rikki) Andrew Cattermole
• Voldemort toHexString Compile Error   kdevel
• tuple-syntax   Dom DiSc
• Google's take on memory safety   Dodobird
• Google's take on memory safety   Dodobird
• Google's take on memory safety   Dodobird
• Google's take on memory safety   electricface
• Voldemort toHexString Compile Error   Salih Dincer
• Memory safe in D   Nick Treleaven
• Memory safe in D   Nick Treleaven
• Spec: can a class method change the type of the object (vtable) ?   Nick Treleaven
• Spec: can a class method change the type of the object (vtable) ?   kinke
• Spec: can a class method change the type of the object (vtable) ?   Dukc
• Spec: can a class method change the type of the object (vtable) ?   Johan
• Memory safe in D   Timon Gehr
• Memory safe in D   Richard (Rikki) Andrew Cattermole
• Memory safe in D   Walter Bright
• Memory safe in D   Walter Bright
• Memory safe in D   Walter Bright
• Memory safe in D   Richard (Rikki) Andrew Cattermole
• tuple-syntax   Basile B.
• core.sys.windows.com.ComObject apparently has wrongly laid out Vtable   Carl Sturtivant
• tuple-syntax   electricface
• tuple-syntax   electricface
• tuple-syntax   electricface
• Memory safe in D   Alex
• Memory safe in D   Alex
• tuple-syntax   Alexandru Ermicioi
• Memory safe in D   Alexandru Ermicioi
• tuple-syntax   electricface
• core.sys.windows.com.ComObject apparently has wrongly laid out Vtable   Kagamin
• tuple-syntax   Dom DiSc
• tuple-syntax   Lance Bachmeier
• core.sys.windows.com.ComObject apparently has wrongly laid out Vtable   Carl Sturtivant
• tuple-syntax   ryuukk_
• core.sys.windows.com.ComObject apparently has wrongly laid out Vtable   Richard (Rikki) Andrew Cattermole
• tuple-syntax   Lance Bachmeier
• Simultaneous video streams of two cameras using DCV   Ferhat Kurtulmuş
• core.sys.windows.com.ComObject apparently has wrongly laid out Vtable   Carl Sturtivant
• core.sys.windows.com.ComObject apparently has wrongly laid out Vtable   Richard (Rikki) Andrew Cattermole
• core.sys.windows.com.ComObject apparently has wrongly laid out Vtable   Carl Sturtivant
• core.sys.windows.com.ComObject apparently has wrongly laid out Vtable   Carl Sturtivant
• tuple-syntax   electricface
• core.sys.windows.com.ComObject apparently has wrongly laid out Vtable   Richard (Rikki) Andrew Cattermole
• core.sys.windows.com.ComObject apparently has wrongly laid out Vtable   Carl Sturtivant
• core.sys.windows.com.ComObject apparently has wrongly laid out Vtable   Carl Sturtivant
• core.sys.windows.com.ComObject apparently has wrongly laid out Vtable   Carl Sturtivant
• core.sys.windows.com.ComObject apparently has wrongly laid out Vtable   Richard (Rikki) Andrew Cattermole
• core.sys.windows.com.ComObject apparently has wrongly laid out Vtable   Zoadian
• core.sys.windows.com.ComObject apparently has wrongly laid out Vtable   Carl Sturtivant
• core.sys.windows.com.ComObject apparently has wrongly laid out Vtable   Carl Sturtivant
• core.sys.windows.com.ComObject apparently has wrongly laid out Vtable   Carl Sturtivant
• core.sys.windows.com.ComObject apparently has wrongly laid out Vtable   Carl Sturtivant
• core.sys.windows.com.ComObject apparently has wrongly laid out Vtable   Carl Sturtivant
• core.sys.windows.com.ComObject apparently has wrongly laid out Vtable   Dom DiSc
• core.sys.windows.com.ComObject apparently has wrongly laid out Vtable   Walter Bright
• core.sys.windows.com.ComObject apparently has wrongly laid out Vtable   Walter Bright
• Lemon Quartz Ring | The Beautiful Ring By Vir Jewels   millyroy06
• core.sys.windows.com.ComObject apparently has wrongly laid out Vtable   Carl Sturtivant
• Memory safe in D   Don Allen
• core.sys.windows.com.ComObject apparently has wrongly laid out Vtable   Carl Sturtivant
• core.sys.windows.com.ComObject apparently has wrongly laid out Vtable   Carl Sturtivant
• core.sys.windows.com.ComObject apparently has wrongly laid out Vtable   Walter Bright
• core.sys.windows.com.ComObject apparently has wrongly laid out Vtable   Walter Bright
• core.sys.windows.com.ComObject apparently has wrongly laid out Vtable   Walter Bright
• This one simple trick allows D programmer use llama.cpp, rust programmers hate him!   evilrat
• core.sys.windows.com.ComObject apparently has wrongly laid out Vtable   Carl Sturtivant
• core.sys.windows.com.ComObject apparently has wrongly laid out Vtable   Carl Sturtivant
• core.sys.windows.com.ComObject apparently has wrongly laid out Vtable   Carl Sturtivant
• core.sys.windows.com.ComObject apparently has wrongly laid out Vtable   Carl Sturtivant
• This one simple trick allows D programmer use llama.cpp, rust programmers hate him!   Andrea Fontana
• Refactoring Code   Salih Dincer
• This one simple trick allows D programmer use llama.cpp, rust programmers hate him!   Andrea Fontana
• This one simple trick allows D programmer use llama.cpp, rust programmers hate him!   Serg Gini
• On the panel discussion at Dconf day 3   surfcrone
• On the panel discussion at Dconf day 3   Richard (Rikki) Andrew Cattermole
• Memory safe in D   Nick Treleaven
• This one simple trick allows D programmer use llama.cpp, rust programmers hate him!   Martyn
• Memory safe in D   Nick Treleaven
• On the panel discussion at Dconf day 3   aberba
• On the panel discussion at Dconf day 3   harakim
• core.sys.windows.com.ComObject apparently has wrongly laid out Vtable   Carl Sturtivant
• core.sys.windows.com.ComObject apparently has wrongly laid out Vtable   Carl Sturtivant
• core.sys.windows.com.ComObject apparently has wrongly laid out Vtable   Carl Sturtivant
• core.sys.windows.com.ComObject apparently has wrongly laid out Vtable   Carl Sturtivant
• Bring back foreach int indexes   Liam McGillivray
• core.sys.windows.com.ComObject apparently has wrongly laid out Vtable   Carl Sturtivant
• core.sys.windows.com.ComObject apparently has wrongly laid out Vtable   Richard (Rikki) Andrew Cattermole
• Bring back foreach int indexes   Walter Bright
• Bring back foreach int indexes   Walter Bright
• On the panel discussion at Dconf day 3   Carl Sturtivant
• Bring back foreach int indexes   Liam McGillivray
• Bring back foreach int indexes   Nick Treleaven
• On the panel discussion at Dconf day 3   electricface
• On the panel discussion at Dconf day 3   Richard (Rikki) Andrew Cattermole
• On the panel discussion at Dconf day 3   H. S. Teoh
• Bring back foreach int indexes   harakim
• Bring back foreach int indexes   deadalnix
• 18% faster build time when using DMD with mimalloc!   ryuukk_
• 18% faster build time when using DMD with mimalloc!   ryuukk_
• Separate dynamic object arrays for multiple instances of overlying object   Quirin Schroll
• Memory safe in D   Quirin Schroll
• 18% faster build time when using DMD with mimalloc!   Johan
• 18% faster build time when using DMD with mimalloc!   ryuukk_
• 18% faster build time when using DMD with mimalloc!   Johan
• speed vs time   user
• This one simple trick allows D programmer use llama.cpp, rust programmers hate him!   Chris Piker
• Memory safe in D   Richard (Rikki) Andrew Cattermole
• 18% faster build time when using DMD with mimalloc!   Dennis
• What are benifits of fildena Fildena double 200mg?   sallow kylie
• Side-Effect System in D   Per Nordlöw
• Memory safe in D   Meta
• Memory safe in D   Lance Bachmeier
• Bring back foreach int indexes   Quirin Schroll
• Bring back foreach int indexes   Steven Schveighoffer
• Bring back foreach int indexes   Steven Schveighoffer
• 18% faster build time when using DMD with mimalloc!   Steven Schveighoffer
• Blazingly 🔥 fast 🚀 memory vulnerabilities, written in 100% safe Rust. 🦀   RazvanN
• Re: Blazingly 🔥 fast 🚀 memory vulnerabilities, written in 100% safe Rust. 🦀   Richard (Rikki) Andrew Cattermole
• Memory safe in D   Richard (Rikki) Andrew Cattermole
• DIP Feedback   Mike Parker
• Side-Effect System in D   Timon Gehr
• Side-Effect System in D   Dukc
• @safe(er) by default forerunner   Bruce Carneal
• Memory safe in D   Walter Bright
• Memory safe in D   Walter Bright
• Memory safe in D   Walter Bright
• Memory safe in D   Walter Bright
• Memory safe in D   Richard (Rikki) Andrew Cattermole
• Memory safe in D   Nick Treleaven
• Memory safe in D   Nick Treleaven
• Blazingly 🔥 fast 🚀 memory vulnerabilities, written in 100% safe Rust. 🦀   Bastiaan Veelo
• Blazingly 🔥 fast 🚀 memory vulnerabilities, written in 100% safe Rust. 🦀   Paul Backus
• d can work with dxhd   monkyyy
• importC: __asm volatile parsing failure - issue or not?   Denis Feklushkin
• importC: __asm volatile parsing failure - issue or not?   Denis Feklushkin
• importC: __asm volatile parsing failure - issue or not?   Denis Feklushkin
• Garbage Collection for Systems Programmers   Adam
• Garbage Collection for Systems Programmers   Anonymouse

Last message date: Sun Mar 31 15:52:26 UTC 2024
Archived on: Sun Mar 31 15:55:05 UTC 2024

• Messages sorted by: [ thread ] [ subject ] [ author ]
• More info on this list...