Re: newer version of Vibe.d tutorial

2023-04-23 Thread zjh via Digitalmars-d-announce

On Sunday, 23 April 2023 at 19:06:44 UTC, Rey Valeza wrote:


I followed your advice. Can you critique the site again? Thanks!



Thank you for sharing.
Everything else is good.



Re: Article on incremental compilation

2023-04-23 Thread Zachary Yedidia via Digitalmars-d-announce
Ah I see, that makes sense. I'll add an edit about that. Thanks 
for the explanation!


Re: newer version of Vibe.d tutorial

2023-04-23 Thread Rey Valeza via Digitalmars-d-announce

On Saturday, 22 April 2023 at 20:27:45 UTC, Rey Valeza wrote:

On Saturday, 22 April 2023 at 01:26:18 UTC, zjh wrote:

On Saturday, 22 April 2023 at 01:23:35 UTC, zjh wrote:

You should create an '`change log`',


Also, please don't paste the content repeatedly, it's too much.


You are the first who commented on that! Thanks!


I followed your advice. Can you critique the site again? Thanks!


Re: newer version of Vibe.d tutorial

2023-04-23 Thread Rey Valeza via Digitalmars-d-announce

On Friday, 21 April 2023 at 18:43:18 UTC, ryuukk_ wrote:

Another suggestion:

https://i.imgur.com/x7nkKXl.png

This is unreadable, please put that on a code block too to make 
it easier on the eyes


Thanks to your comments, the site is a lot more readable now!


Re: Article on incremental compilation

2023-04-23 Thread Steven Schveighoffer via Digitalmars-d-announce

On 4/22/23 7:33 PM, Zachary Yedidia wrote:

Hi everyone,

I've been tinkering with setting up incremental compilation in my D 
projects by using `.di` files to ensure that a module is only recompiled 
if its interface changes (not its implementation). I've written an 
article about it here: 
https://zyedidia.github.io/blog/posts/4-incremental-d-knit/. Hopefully 
you find it interesting! Thanks!


Nice! Your build system sounds pretty cool.

On your section on "Areas for improvements in D interface files":

The previous section holds the answer -- templates. Templates must be 
included in full because they are instantiated by the caller. But a 
template can still use:


* private variables/functions
* private types
* private imports

etc. Basically anything that can be used in the implementation. The only 
thing that's hidden is non-template function implementations.


In order to avoid copying those things, the compiler would have to prove 
that no template inside the module can use these things.


One possible mechanism could be if *no* templates exist, it could 
exclude them. But to determine whether an existing template might use 
them, I believe is the halting problem.


So we are stuck with it.

-Steve


Re: newer version of Vibe.d tutorial

2023-04-23 Thread Rey Valeza via Digitalmars-d-announce

On Friday, 21 April 2023 at 18:43:18 UTC, ryuukk_ wrote:

Another suggestion:

https://i.imgur.com/x7nkKXl.png

This is unreadable, please put that on a code block too to make 
it easier on the eyes


Thanks to your comments, the site is a lot more readable now!