huskyxahusky / ucgorgeous

Swift Macros. The coolest methods "copy" classes/structures, which is especially useful in the functional programming paradigm...

• 👋 Hi, I’m Vladimir Shapovalov. By day, I am a simple, even a very simple doctor. However, as the darkness deepens, I become an amateur programmer, coding on the wings of the night.
• 👀 I’m interested in ... Everything, I'm interested in everything. In medicine - the abyss of information. It's great that programmers have something to read as well!
• 🌱 I’m currently learning swift, JS (and everything connected with it).
• 💞️ I’m looking to collaborate on ... anyone who will make me better.
• 📫 How to reach me ... here

ucgorgeous's Issues

Adding file to pack

I want to move the utilitarian functions from UCgorgeousMacro.swift into a separate file (for example, in Utility.swift). But I don't know how to do this. When I create a new file, the package does not see it. I know that I need to connect it in Package.swift, but I can't do it correctly.
I'll be glad if someone can tell me how to do this, preferably with an example based on my Package.swift.

@ClassCopy && @StructCopy and computed properties

The copy method must ignore the presence of computed properties!
It is obvious. However, it is currently not clear how to do this.

Inconsistent initialization error

If properties are declared in a class in one order, and in the initializer in another, then the precompiler will throw an error.
To avoid this, the user needs to initialize the properties in the same order in which they were declared.

Or we need to enhance the macro so that it is based on the initializer sequence.
However, difficulties may arise here if there are several initializers...