This is actually a rather annoying problem.
This is actually a rather annoying problem. This is what I'm doing temporarily (all fields have the "omitempty" tag): Fetch struct A from DB Unmarshal JSON data into &A Unset read-only fields of A Save A to DB It's very inefficient but it beats dealing with bugs caused by various flags not being set (or being unset). I'll switch to using pointers to boolean, int and string since most other (non-trivial) fields are pointers anyway. I'm not happy about the indirection, but it's certainly much faster than the current database roundtrip I'm performing. And for anyone shouting 'Rust' - there's always going to be that perfect language out there, at the end of the rainbow.
Posted by optymizer on May 30, 2014, 12:09 AM
Tags
Related issues
- Not sure what you suggest to do.
- Why is this not yet published on the official website and why is there no CVE?
- The biggest problem with having an LLM do this, from what I've observed of at least frontier models, is that the way they are trained...
- The biggest problem with MOND is that it was hand-crafted with additional parameters simply to fit the data.
- (My comment is about detached houses).
- The biggest problem with this is that I can't run my company's own internal benchmarks against this API, because they will be trained int...
Raise real-world problems, find people facing the same issue, and discuss solutions.9,500 issues0 comments
hackernews (Other)
Not sure what you suggest to do.
NewWhy is this not yet published on the official website and why is there no CVE?
NewThe biggest problem with having an LLM do this, from what I've observed of at least frontier models, is that the way they are trained...
The biggest problem with MOND is that it was hand-crafted with additional parameters simply to fit the data.
(My comment is about detached houses).
The biggest problem with this is that I can't run my company's own internal benchmarks against this API, because they will be trained int...
> steer Claude away from over-engineering parts of the system in response to hypothetical concerns.
Why is there no comparison with FLUX 3 Image?
This is actually a rather annoying problem.
This is actually a rather annoying problem. This is what I'm doing temporarily (all fields have the "omitempty" tag): Fetch struct A from DB Unmarshal JSON data into &A Unset read-only fields of A Save A to DB It's very inefficient but it beats dealing with bugs caused by various flags not being set (or being unset). I'll switch to using pointers to boolean, int and string since most other (non-trivial) fields are pointers anyway. I'm not happy about the indirection, but it's certainly much faster than the current database roundtrip I'm performing. And for anyone shouting 'Rust' - there's always going to be that perfect language out there, at the end of the rainbow.
Comments (0)
No comments yet. Start the discussion.