More granular IR format #203
AttilaMihaly
started this conversation in
Ideas
Replies: 1 comment
-
I have a bunch of thoughts on this. Rather than wait until I've collected them all, I'll drip them in. My main hypothesis is that a file-based format will be more accessible for new developers and tool writers. Some thoughts:
Those are my main points for now. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Morphir tools currently communicate through a single JSON file that contains the IR for all the modules within a package and also the package's dependencies. While this is a simple approach that works the community brought up the idea of creating a more granular format that breaks up the IR into smaller files.
We had a few discussions about the implementation details and it seems to be feasible but to come up with the best design we need spell-out specific requirements. So in this discussion I would like to invite the community to share what specific advantages we are hoping to get from a more granular IR structure.
To get things started, I know of one particular advantage:
What other benefit are we hoping to achieve?
@DamianReeves, @stephengoldbaum
Beta Was this translation helpful? Give feedback.
All reactions