-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
we should have semantics in instanceTechnique along with values #110
Comments
Presumably with the same syntax, i.e. an array? :-p |
I was waiting for you to get back there.. ;) Now that we don't need to specify either So I extend a bit the topic of this bug for a moment.... We have to make a trade-off: have to choose between the solutions that "looks good" i.e objects versus the most pratical one i.e the array. Would you guys be OK to switch from:
to
What do you think ? @tparisi I guess what's your side here ;) |
@fabrobinet I think you meant that 2. looks obviously better. Of course I prefer #2. We're doing gets on the keys all over the place anyway, so IMO doing one more foreach won't kill an implementation. An array is a bit more efficient but that efficiency is probably going to be eclipsed in any practical implementation by code that error-checks the input and other processing, anyway. Long story short I prefer #2. |
yeah, I meant 2. |
I know @tparisi is OK, @RemiArnaud @pjcozzi OK too ? If yes I will makes changes in the converter. |
Ok, will implement this one soon. |
Sorry for the delay here, but I am strongly for 2 as well. In fact, I had this exact feedback in my notes from when I redid my implementation a little while back. |
Ok thanks for confirming Patrick. I'll make it sometime this week. |
6c39102 ready in dev-1 branch |
pushed on master |
@fabrobinet schema is updated, let's close. |
No description provided.
The text was updated successfully, but these errors were encountered: