You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 13, 2025. It is now read-only.
Several functions, such as the one below, do not return an error.
funcNewMessage(v []byte) *Message {
The nil value is used (such as msg == nil to determine success failure. This appears to lead to awkward error handling and the at least one use of a Fatal call.
I am new to this project, thus if there is a reason inherent to the workings of HL7 then that is something I am now aware of.
Excluding a hard requirement, what is the reason for not returning the idiomatic (and useful) result, err?
Along this lines, it seems like many calls do not handle errors. Is this intentional or a factor of time?
Several functions, such as the one below, do not return an error.
The
nilvalue is used (such asmsg == nilto determine success failure. This appears to lead to awkward error handling and the at least one use of aFatalcall.I am new to this project, thus if there is a reason inherent to the workings of HL7 then that is something I am now aware of.
Excluding a hard requirement, what is the reason for not returning the idiomatic (and useful)
result, err?Along this lines, it seems like many calls do not handle errors. Is this intentional or a factor of time?