On Thu, May 27, 2021 at 9:27 PM cheng dong <qq451954...@gmail.com> wrote:
> problem is compiler often don't known how programs organize objects, or, > some memory pattern could not be known at compile time. > and sometimes, delete point is very obvious in some programming models. > finally i think developer should take their risk taking some unsafe > operations by himself (like rust lang?) You are proposing the introduction of a "HCF" (Halt, Catch Fire) instruction. You also wrote "delete point is very obvious in some programming models." For those cases it should be equally obvious to the Go compiler. It shouldn't be necessary for the programmer to annotate the object in that case. I also fail to see what your first point has to do with your proposal. There is no way, other than for a hypothetical computer language I have never seen, for the compiler to know about the dynamic memory allocation pattern when the program runs. Your proposal does not address that problem. -- Kurtis Rader Caretaker of the exceptional canines Junior and Hank -- 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/CABx2%3DD9sw8_sR1%2BdGkqfFz_nf2TYZ2fFW3q_vuMPQ6UoeMiqKQ%40mail.gmail.com.
