-
Notifications
You must be signed in to change notification settings - Fork 523
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
[C#] - Invalid generated code for string field. #955
Comments
@JPWatson, what are your thoughts? |
I have the same problem. |
@ZachBray Can you look at this? |
I came across this a few weeks back as well. It is already fixed in #948: |
We now explore more of the "schema space", as we generate lengths of different encodings. It surfaces an issue, reported in real-logic#955, which was fixed in another outstanding PR's commit: 3885a63.
We now explore more of the "schema space", as we generate lengths of different encodings. It surfaces an issue, reported in real-logic#955, which was fixed in another outstanding PR's commit: 3885a63.
We now explore more of the "schema space", as we generate lengths of different encodings. It surfaces an issue, reported in real-logic#955, which was fixed in another outstanding PR's commit: 3885a63.
Closing. The fix is merged and part of |
We now explore more of the "schema space", as we generate lengths of different encodings. It surfaces an issue, reported in real-logic#955, which was fixed in another outstanding PR's commit: 3885a63.
We now explore more of the "schema space", as we generate lengths of different encodings. It surfaces an issue, reported in real-logic#955, which was fixed in another outstanding PR's commit: 3885a63.
We now explore more of the "schema space", as we generate lengths of different encodings. It surfaces an issue, reported in real-logic#955, which was fixed in another outstanding PR's commit: 3885a63.
We now explore more of the "schema space", as we generate lengths of different encodings. It surfaces an issue, reported in real-logic#955, which was fixed in another outstanding PR's commit: 3885a63.
Hi guys,
I'm using the SbeTools (I've tried the one in the nuget package and with the latest version here in git), but the generated code is invalid with the template i'm running. The DirectBuffer class don't have the signature method for the generated code (Uint8Put).
The code generated below:
The DirectBuffer code:
Could you guys check?
Thanks.
The text was updated successfully, but these errors were encountered: