You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While working on Zig bindings, i was translating quite a bit of C to Zig, so i also tried and structure the code in a way, that i have quite a bit of files.
A common pattern that arose is the following:
constRegister=@import("register.zig").Register; // This file does not exist (yet)// ....constSomething=externstruct {
reg: Register,
// ...
};
I would think that a code action to just create the file in the corresponding folder would be a great improvement for this specific workflow, but even in other workflows this would make a lot of sense in my opinion.
Being more concrete
Let's imagine the following folder-structure:
── src
├── linux
│ └── import.zig
└── windows
└── import.zig
and then imagine within the linux/import.zig folder the following Line: const fs = @import("file_system.zig");
It would just make sense that a code action would create the file in the assumed folder, so that it would result in:
── src
├── linux
│ ├── file_system.zig
│ └── import.zig
└── windows
└── import.zig
Another point i'd say supporting this idea is, that probably most people are mostly working in the root of their project, so it would always be a bit cumbersome for us to create the file in the corresponding folder.
The text was updated successfully, but these errors were encountered:
Story
While working on Zig bindings, i was translating quite a bit of C to Zig, so i also tried and structure the code in a way, that i have quite a bit of files.
A common pattern that arose is the following:
I would think that a code action to just create the file in the corresponding folder would be a great improvement for this specific workflow, but even in other workflows this would make a lot of sense in my opinion.
Being more concrete
Let's imagine the following folder-structure:
and then imagine within the
linux/import.zig
folder the following Line:const fs = @import("file_system.zig");
It would just make sense that a code action would create the file in the assumed folder, so that it would result in:
Another point i'd say supporting this idea is, that probably most people are mostly working in the root of their project, so it would always be a bit cumbersome for us to create the file in the corresponding folder.
The text was updated successfully, but these errors were encountered: