Re: [go-nuts] Calling Once (in the code)

[dc0d]

How can that get applied here (The Halting Problem)? We use functions 
everywhere and this is the same as we already do (with same level of 
probability for Halting Problem).

What I do currently:

1 - abstracting some parts of a long function in another function.
2 - the name of that second function starts with a Japanese character 
(because I have not those characters and I can not type them by accident)

This way I have a function that is called just once "in the code" but the 
caller function may call this child function as much as it needs.

On Friday, August 11, 2017 at 12:38:04 AM UTC+4:30, Jan Mercl wrote:
>
> On Thu, Aug 10, 2017 at 10:03 PM dc0d  
> wrote:
>
> > Is there a tool/linter to check if a private package function gets 
> called exactly once in the code? 
>
> Good luck with solving the halting problem ;-)
>
> -- 
>
> -j
>

-- 
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.

Re: [go-nuts] Calling Once (in the code)

[Jan Mercl]

On Thu, Aug 10, 2017 at 10:03 PM dc0d  wrote:

> Is there a tool/linter to check if a private package function gets called
exactly once in the code?

Good luck with solving the halting problem ;-)

-- 

-j

-- 
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.