digitalmars.D.learn - Compiler module import graph
- frame (6/6) Mar 13 2021 Is there a tool to view module import graph?
- ag0aep6g (5/11) Mar 13 2021 `dmd -deps` shows what imports what.
- frame (3/16) Mar 13 2021 For some reason the only output I get is 'interface function ...
- frame (3/22) Mar 13 2021 Ok, I was stupid forget the -m64 switch and had a size_t/ulong
- Eugene Wissner (2/8) Mar 13 2021 An external tool: https://github.com/funkwerk/depend.
- frame (2/11) Mar 13 2021 Thanks! I will try this out.
Is there a tool to view module import graph? The compiler verbose output shows that the module is imported/parsed but not why. I wan't to avoid unnecessary imports to speed up compile times or avoid issues if the module contents are not fully compatible with the current compile target being in development.
Mar 13 2021
On 13.03.21 15:20, frame wrote:Is there a tool to view module import graph? The compiler verbose output shows that the module is imported/parsed but not why. I wan't to avoid unnecessary imports to speed up compile times or avoid issues if the module contents are not fully compatible with the current compile target being in development.`dmd -deps` shows what imports what. https://dlang.org/dmd-linux.html#switch-deps Be aware that there is a bug where DMD misses some edges in the graph: https://issues.dlang.org/show_bug.cgi?id=21238
Mar 13 2021
On Saturday, 13 March 2021 at 14:30:52 UTC, ag0aep6g wrote:On 13.03.21 15:20, frame wrote:For some reason the only output I get is 'interface function ... is not implemented' errors if I run this switch.Is there a tool to view module import graph? The compiler verbose output shows that the module is imported/parsed but not why. I wan't to avoid unnecessary imports to speed up compile times or avoid issues if the module contents are not fully compatible with the current compile target being in development.`dmd -deps` shows what imports what. https://dlang.org/dmd-linux.html#switch-deps Be aware that there is a bug where DMD misses some edges in the graph: https://issues.dlang.org/show_bug.cgi?id=21238
Mar 13 2021
On Saturday, 13 March 2021 at 14:55:20 UTC, frame wrote:On Saturday, 13 March 2021 at 14:30:52 UTC, ag0aep6g wrote:Ok, I was stupid forget the -m64 switch and had a size_t/ulong bug in an interface. Thanks.On 13.03.21 15:20, frame wrote:For some reason the only output I get is 'interface function ... is not implemented' errors if I run this switch.Is there a tool to view module import graph? The compiler verbose output shows that the module is imported/parsed but not why. I wan't to avoid unnecessary imports to speed up compile times or avoid issues if the module contents are not fully compatible with the current compile target being in development.`dmd -deps` shows what imports what. https://dlang.org/dmd-linux.html#switch-deps Be aware that there is a bug where DMD misses some edges in the graph: https://issues.dlang.org/show_bug.cgi?id=21238
Mar 13 2021
On Saturday, 13 March 2021 at 14:20:01 UTC, frame wrote:Is there a tool to view module import graph? The compiler verbose output shows that the module is imported/parsed but not why. I wan't to avoid unnecessary imports to speed up compile times or avoid issues if the module contents are not fully compatible with the current compile target being in development.An external tool: https://github.com/funkwerk/depend.
Mar 13 2021
On Saturday, 13 March 2021 at 14:41:48 UTC, Eugene Wissner wrote:On Saturday, 13 March 2021 at 14:20:01 UTC, frame wrote:Thanks! I will try this out.Is there a tool to view module import graph? The compiler verbose output shows that the module is imported/parsed but not why. I wan't to avoid unnecessary imports to speed up compile times or avoid issues if the module contents are not fully compatible with the current compile target being in development.An external tool: https://github.com/funkwerk/depend.
Mar 13 2021