Protocol inheritance doesn't work on lib #99
Replies: 4 comments
-
Sure, let's look into it. If I understand you, Gryphon is translating something like // gryphon inspect
public protocol DisplayComponent : Component { } When you run it with the comment, Gryphon should print some information about this protocol to the command line. Then, you can paste that information here and I'll take a look at it. If you're using Gryphon through Xcode (instead of the command line) you can probably see the output by hitting Command+9 and selecting the latest |
Beta Was this translation helpful? Give feedback.
-
Hey @IgorMaineti, any news on this? Did it work out? |
Beta Was this translation helpful? Give feedback.
-
Hello @vinivendra, sorry for the late answer, the holidays came and I totally forgot about this discussion. We observed a strange behaviour, the transpilation worked fine when we ran Gryphon through Xcode but it wasn't working building through the terminal, however, yesterday we all updated everything again and it worked flawslessly. Thanks for everything, you can close the discussion 😄 . |
Beta Was this translation helpful? Give feedback.
-
No worries, just wanted to make sure everything was OK :) |
Beta Was this translation helpful? Give feedback.
-
Recently I opened a pull request to implement protocol inheritance #95 and it worked fine on the test class, however, after the merge I installed the HEAD version from brew and it didn't work 😞.
The code I wrote on the test class:
public protocol DisplayComponent : Component { }
Output:
interface DisplayComponent: Component { }
But, if I write the same protocol on my lib, gryphon won't translate their inheritances, could you help us, please?
Beta Was this translation helpful? Give feedback.
All reactions