On Monday, 14 November 2022 at 20:37:12 UTC, kdevel wrote:
On Monday, 14 November 2022 at 17:08:38 UTC, Gavin Ray wrote:
Just came here to say I hit the same bug, here's my import
list:
* https://issues.dlang.org/show_bug.cgi?id=19937
object._d_assert_fail linker error if compiling with
-ch
Doing my research, the only option I see is by using 'setpgid'
from 'core.sys.posix.unistd'
and setting the foreground process using 'tcsetpgrp' from the
same module, but I don't know how to go about doing that with the
'std.process.spawnProcess', I'm writing a shell and the purpose
of this is
On Thu, Nov 17, 2022 at 10:16:04PM +, jwatson-CO-edu via
Digitalmars-d-learn wrote:
> On Thursday, 17 November 2022 at 21:05:43 UTC, H. S. Teoh wrote:
[...]
> > struct Atom {
> > F_Type kind;
> > union { // anonymous union
> > Atom* car
On Thursday, 17 November 2022 at 21:19:56 UTC, Petar Kirov
[ZombineDev] wrote:
On Thursday, 17 November 2022 at 20:54:46 UTC, jwatson-CO-edu
wrote:
I have an implementation of the "[Little
Scheme](https://mitpress.mit.edu/9780262560993/the-little-schemer/)" educational programming language writt
On Thursday, 17 November 2022 at 21:05:43 UTC, H. S. Teoh wrote:
Question:
**Where do I begin my consolidation of space within `Atom`?
Do I use
unions or variants?**
In this case, since you're already keeping track of what type
of data is being stored in an Atom, use a union:
stru
I just pushed a D implementation of "[Little
Scheme](https://mitpress.mit.edu/9780262560993/the-little-schemer/)", which is a limited educational version of [Scheme](https://en.wikipedia.org/wiki/Scheme_(programming_language)), to [GitHub](https://github.com/jwatson-CO-edu/SPARROW).
_Here I woul
On Thursday, 17 November 2022 at 20:54:46 UTC, jwatson-CO-edu
wrote:
I have an implementation of the "[Little
Scheme](https://mitpress.mit.edu/9780262560993/the-little-schemer/)" educational programming language written in D, [here](https://github.com/jwatson-CO-edu/SPARROW)".
It has many probl
On Thu, Nov 17, 2022 at 08:54:46PM +, jwatson-CO-edu via
Digitalmars-d-learn wrote:
[...]
> ```d
> enum F_Type{
> CONS, // Cons pair
> STRN, // String/Symbol
> NMBR, // Number
> EROR, // Error object
> BOOL, // Boolean value
> FUNC, // Function
> }
>
> struct Atom{
>
I have an implementation of the "[Little
Scheme](https://mitpress.mit.edu/9780262560993/the-little-schemer/)" educational programming language written in D, [here](https://github.com/jwatson-CO-edu/SPARROW)".
It has many problems, but the one I want to solve first is the
size of the "atoms" (un
On 11/16/22 11:25 PM, Daniel Donnelly wrote:
I have SubclassOf derived from PosetRelation. For any poset relation,
the transitivity law applies, however, I'd like to return the correct type:
```
PosetRelation transitivity(PosetRelation R, PosetRelation S)
{
if (R.op == S.op)
On Thursday, 17 November 2022 at 06:48:13 UTC, Daniel Donnelly,
Jr. wrote:
On Thursday, 17 November 2022 at 05:21:05 UTC, MorteFeuille123
wrote:
On Thursday, 17 November 2022 at 04:25:13 UTC, Daniel
Donnelly, Jr. wrote:
[...]
You can use TypeInfoClass:
[...]
I don't get it - you never made
On Thursday, 17 November 2022 at 04:39:35 UTC, thebluepandabear
wrote:
I am debating whether or not I should add getter methods to
these properties. On one hand, it will inflate the codebase by
a lot, on the other hand -- in other languages like Java it is
a good practice
D has far less need
On Thursday, 17 November 2022 at 04:39:35 UTC, thebluepandabear
wrote:
...
It's not a lot of code that has been added but if you have a
class with say 10 different fields, adding getter methods would
definitely increase the code size by a lot, so what are you
guys thoughts on this?
Food for
(and will never need) that controlled access.
Thanks. BTW the code is not Java, it is 100% D.
On Thursday, 17 November 2022 at 04:39:35 UTC, thebluepandabear
wrote:
I am creating a TUI library and I have a class with the
following constant fields:
```
class Label : Renderable {
const string text;
const TextAlignment textAlignment;
const Color color;
this(Dimensions dime
15 matches
Mail list logo