If it offers consistency within your product then I think it definitely makes sense for everybody involved in working with this code. The people involved will know the business related terminology, I assume.
I think the key here is to provide consistent documentation. Then you have absolutely nothing to worry about. What you are asking is perfectly ok! On Thursday, 21 September 2017 20:43:14 UTC+2, M2 wrote: > > We have the same library in multiple languages. > > All the other languages name a specific class/struct fooContext. In Go > that data structure stores some metadata to be propagated by the > "context".Context? > Is it ok to name it "fooContext" in Go also to stay consistent with the > other languages even if it doesn't implement the "context".Context > interface or is it too confusing for Go users and needs to be named > something else? > > In general is it ok to name something that is not a context xyzContext? > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
