Do you feel your GOLANG API implementations allows your API's
and functions to evolve and grow? Personally, positional args has pissed me
off for years when a proven simple solution has never been adopted by most
Unix programming languages (except Javascript). Most notably, it's missing
from GOLANG.
Everyone here understands and uses os.open from the os package. For
argument's sake, let's say os.open() is your responsibility to integrate
nosql, memory files, compression, encryption, btree, key indexed files and
more. How do you modify os.open( ) to integrate these file related
features? This was solved years ago in languages not used in Unix
using keyword arguments that also included positional. For example:
func os.open(name string, memoryfile= bool, compress= bool, btree{
btree_optons string }, encrypt{ key= string }, nosql{ nosql_options string
} ) (*File, error)
os.open('myfile.txt', encrypt{ key='abc' }, compress=true)
The os.open args 1, 3 and 5 would be set from the specified arguments.
Is this something that others need and I should pursue or should I just
forget it? Proposal https://github.com/golang/go/issues/62078 was closed
with "I don't see anything concrete being proposed here.". If I should
pursue this, should I reword it or reduce it to this Email?
Thanks, Jon.
--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/golang-nuts/CAByJhJnkuai27VNiE6PraU9-5hoO85Hm__0UQJrT75a7KqD8uw%40mail.gmail.com.
