Monorepo?

Iain Buclaw ibuclaw at gdcproject.org
Tue Feb 7 00:04:42 UTC 2023


On Monday, 6 February 2023 at 23:49:54 UTC, Adam D Ruppe wrote:
> On Monday, 6 February 2023 at 23:42:01 UTC, Iain Buclaw wrote:
>> Goodbye -release, goodbye -dip1000, goodbye -checkaction=, 
>> goodbye -preview=, goodbye -debug=, goodbye -unittest, goodbye 
>> -version=, goodbye -allinst...
>
> i have a potential solution
>
> http://dpldocs.info/this-week-in-d/Blog.Posted_2022_11_14.html#redesign-for-template-emission-woes

Agreed that none of them are strictly bugs once you explain the 
rationale.

There are historically two ways to go about it.

1. Reference a template repository during building of each 
module, package, library, project, ...; whichever way your build 
is broken down into.  Add templates to the repo as you progress 
through building your project.

2. Go gung-ho with emissions, relying on "used" flags to 
determine whether any calls/address references to the symbol 
actually remain in the graph (after inlining), and prune it all 
away before writing to assembly/object file.


More information about the Digitalmars-d mailing list