On 5/6/20 8:28 PM, SealabJaster wrote:
On Wednesday, 11 December 2019 at 12:04:04 UTC, SealabJaster wrote:
Final post of this series (also sorry for the necro, but it's probably
better than making a new post):
07.05.2020 18:03, jmh530 пишет:
I make mistakes all the time. I find that saying dumb things out loud
often will help me learn and make fewer mistakes in the future.
Totally agree
On Thursday, 7 May 2020 at 14:15:07 UTC, Greatsam4sure wrote:
[snip]
Yeah, I thought it looked good.
I make mistakes all the time. I find that saying dumb things out
loud often will help me learn and make fewer mistakes in the
future.
On Thursday, 7 May 2020 at 00:28:10 UTC, SealabJaster wrote:
On Wednesday, 11 December 2019 at 12:04:04 UTC, SealabJaster
wrote:
Final post of this series (also sorry for the necro, but it's
probably better than making a new post):
On Wednesday, 11 December 2019 at 12:04:04 UTC, SealabJaster
wrote:
Final post of this series (also sorry for the necro, but it's
probably better than making a new post):
https://bradley.chatha.dev/BlogPost/JsonSerialiser/6-mixin-template-automate-dlang-tutorial-metaprogramming
Pretty
On Wednesday, 4 December 2019 at 03:13:28 UTC, SealabJaster wrote:
..
Final post of the year (and for a while) is out:
https://bradley.chatha.dev/Home/Blog?post=JsonSerialiser5
Once I've worked on the website's design + other things I want to
get done, then I'll finish off the series with
On Saturday, 23 November 2019 at 22:38:22 UTC, SealabJaster wrote:
On Tuesday, 12 November 2019 at 09:15:28 UTC, SealabJaster
wrote:
...
Just wanted to quickly explain the delay for the next post.
Basically just boils down to energy levels being non-existant,
and run.dlang.io still being
On Tuesday, 12 November 2019 at 09:15:28 UTC, SealabJaster wrote:
And if you do allow things such as letting classes have a
'deserialise' member function which can be overloaded, you
still need to create or be given an instance of the class
beforehand, which brings things back around to the
On Tuesday, 12 November 2019 at 09:15:28 UTC, SealabJaster wrote:
...
Just wanted to quickly explain the delay for the next post.
Basically just boils down to energy levels being non-existant,
and run.dlang.io still being broken (Don't want to have a backlog
of snippets to make).
On 11/12/19 4:15 AM, SealabJaster wrote:
On Monday, 11 November 2019 at 16:56:31 UTC, Steven Schveighoffer wrote:
The tough part about serializing classes is if the class is not final,
how do you serialize the derived data. It requires some sort of user
help to
tell it how to get at the data.
On Monday, 11 November 2019 at 16:56:31 UTC, Steven Schveighoffer
wrote:
On 10/30/19 8:05 PM, SealabJaster wrote:
...
Looks like a great idea! Sounds very similar to what I've been
learning over the past 5 years or so.
See my dconf presentation from this year.
I had a quick skim, and
On 11/10/19 5:50 PM, JN wrote:
On Sunday, 10 November 2019 at 10:22:17 UTC, SealabJaster wrote:
Next post is out, I feel kind of iffy over how I went over classes,
but I think for the most part it came out ok. I probably won't touch
classes specifically in any future post though, unless I can
On 10/30/19 8:05 PM, SealabJaster wrote:
https://bradley.chatha.dev/Home/Blog?post=JsonSerialiser1
Currently only the first post is out, as I'd like to collect feedback
before writing any more.
The series is aimed at people new to D, or people who have heard of D,
but haven't really
On Sunday, 10 November 2019 at 10:22:17 UTC, SealabJaster wrote:
Next post is out, I feel kind of iffy over how I went over
classes, but I think for the most part it came out ok. I
probably won't touch classes specifically in any future post
though, unless I can think of something interesting
On Sunday, 3 November 2019 at 08:37:07 UTC, SealabJaster wrote:
...
Next post is out, I feel kind of iffy over how I went over
classes, but I think for the most part it came out ok. I probably
won't touch classes specifically in any future post though,
unless I can think of something
On Monday, 4 November 2019 at 08:25:11 UTC, Patrick Schluter
wrote:
I don't get why it confuses people.
In all languages I know (C, C++, Java, Pascal, etc..) they are
used to associate a compile time symbols with some quantities,
i.e. the definition of constants.
When an enumeration only
On Monday, 4 November 2019 at 08:25:11 UTC, Patrick Schluter
wrote:
On Sunday, 3 November 2019 at 21:35:18 UTC, JN wrote:
On Sunday, 3 November 2019 at 08:37:07 UTC, SealabJaster wrote:
On Sunday, 3 November 2019 at 08:35:42 UTC, SealabJaster
wrote:
On Friday, 1 November 2019 at 21:14:56 UTC,
On Sunday, 3 November 2019 at 21:35:18 UTC, JN wrote:
On Sunday, 3 November 2019 at 08:37:07 UTC, SealabJaster wrote:
On Sunday, 3 November 2019 at 08:35:42 UTC, SealabJaster wrote:
On Friday, 1 November 2019 at 21:14:56 UTC, SealabJaster
wrote:
...
Sorry, seems it cut out the first half of
On Sunday, 3 November 2019 at 08:37:07 UTC, SealabJaster wrote:
On Sunday, 3 November 2019 at 08:35:42 UTC, SealabJaster wrote:
On Friday, 1 November 2019 at 21:14:56 UTC, SealabJaster wrote:
...
Sorry, seems it cut out the first half of that reply.
New posts are out, and I don't want to
On Sunday, 3 November 2019 at 08:35:42 UTC, SealabJaster wrote:
On Friday, 1 November 2019 at 21:14:56 UTC, SealabJaster wrote:
...
Sorry, seems it cut out the first half of that reply.
New posts are out, and I don't want to spam Announce with new
threads, so I'm just replying to this one.
On Friday, 1 November 2019 at 21:14:56 UTC, SealabJaster wrote:
...
I've also made some changes to post #1 based on my last two
comments on this thread.
I'd also like to clarify that the main purpose of this series is
to demonstrate some of the thing of what D's metaprogramming can
do, via
On Friday, 1 November 2019 at 11:29:11 UTC, Ethan wrote:
You also want to catch const(char)[] and just plain char[] for
JSON serialisation purposes. So a template constraint that
catches all those is what you want instead of just is( T ==
string ).
I was definitely thinking of putting that
On Friday, 1 November 2019 at 10:39:42 UTC, Jacob Carlborg wrote:
On Thursday, 31 October 2019 at 00:05:06 UTC, SealabJaster
wrote:
https://bradley.chatha.dev/Home/Blog?post=JsonSerialiser1
FYI, string is a built-in type.
I feel it's more of a weird gray area. As Ethan said it's more
On Friday, 1 November 2019 at 12:50:09 UTC, Jacob Carlborg wrote:
It's an alias, but what it's aliased to is a built-in type.
A *slice* of a built-in type *with qualifiers*.
The only way to simplify that description is to call it
"syntactic sugar". "Built-in type" to describe the entire
On Friday, 1 November 2019 at 11:29:11 UTC, Ethan wrote:
string is immutable(char)[], as we all know. Syntactic sugar,
not exactly a built in type but treating it like one is often
valuable.
It's an alias, but what it's aliased to is a built-in type.
--
/Jacob Carlborg
On Friday, 1 November 2019 at 10:39:42 UTC, Jacob Carlborg wrote:
FYI, string is a built-in type.
string is immutable(char)[], as we all know. Syntactic sugar, not
exactly a built in type but treating it like one is often
valuable.
To follow on from this, I'll share my experience with
On Thursday, 31 October 2019 at 00:05:06 UTC, SealabJaster wrote:
https://bradley.chatha.dev/Home/Blog?post=JsonSerialiser1
FYI, string is a built-in type.
Regarding exercise 2. I would be very careful with deserializing
a single character from JSON. First, because JSON doesn't support
On 10/31/2019 2:51 AM, SealabJaster wrote:
On Thursday, 31 October 2019 at 07:38:46 UTC, Walter Bright wrote:
Looks like a very nice initiative! Looking forward to more!
A thought - host it on github? That way people can easily contribute
suggestions to it. You'd be in charge, of course, with
On Thursday, 31 October 2019 at 09:11:59 UTC, Paolo Invernizzi
wrote:
On Thursday, 31 October 2019 at 09:07:18 UTC, GreatSam4sure
wrote:
On Thursday, 31 October 2019 at 09:02:07 UTC, Paolo Invernizzi
wrote:
On Thursday, 31 October 2019 at 00:05:06 UTC, SealabJaster
wrote:
[...]
Great Job,
On Thursday, 31 October 2019 at 07:38:46 UTC, Walter Bright wrote:
Looks like a very nice initiative! Looking forward to more!
A thought - host it on github? That way people can easily
contribute suggestions to it. You'd be in charge, of course,
with what to do with those suggestions.
Happy
On Thursday, 31 October 2019 at 06:35:07 UTC, GreatSam4sure wrote:
On Thursday, 31 October 2019 at 00:05:06 UTC, SealabJaster
wrote:
https://bradley.chatha.dev/Home/Blog?post=JsonSerialiser1
Currently only the first post is out, as I'd like to collect
feedback before writing any more.
[...]
On Thursday, 31 October 2019 at 09:07:18 UTC, GreatSam4sure wrote:
On Thursday, 31 October 2019 at 09:02:07 UTC, Paolo Invernizzi
wrote:
On Thursday, 31 October 2019 at 00:05:06 UTC, SealabJaster
wrote:
https://bradley.chatha.dev/Home/Blog?post=JsonSerialiser1
Currently only the first post is
On Thursday, 31 October 2019 at 09:02:07 UTC, Paolo Invernizzi
wrote:
On Thursday, 31 October 2019 at 00:05:06 UTC, SealabJaster
wrote:
https://bradley.chatha.dev/Home/Blog?post=JsonSerialiser1
Currently only the first post is out, as I'd like to collect
feedback before writing any more.
On Thursday, 31 October 2019 at 00:05:06 UTC, SealabJaster wrote:
https://bradley.chatha.dev/Home/Blog?post=JsonSerialiser1
Currently only the first post is out, as I'd like to collect
feedback before writing any more.
[...]
Great Job, keep pushing!
If you don't know it, I suggest to have
Looks like a very nice initiative! Looking forward to more!
A thought - host it on github? That way people can easily contribute suggestions
to it. You'd be in charge, of course, with what to do with those suggestions.
https://bradley.chatha.dev/Home/Blog?post=JsonSerialiser1
Currently only the first post is out, as I'd like to collect
feedback before writing any more.
The series is aimed at people new to D, or people who have heard
of D, but haven't really explored its metaprogramming too much,
hence
36 matches
Mail list logo
