From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <39c6e4b135cec83b2095612a1e178536@ladd.quanstro.net> Date: Mon, 3 Jun 2013 18:38:28 +0100 Message-ID: From: Charles Forsyth To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001a11c2443cb9c4e804de436efd Subject: Re: [9fans] Go and 21-bit runes (and a bit of Go status) Topicbox-Message-UUID: 625d3a2a-ead8-11e9-9d60-3106f5b1d025 --001a11c2443cb9c4e804de436efd Content-Type: text/plain; charset=UTF-8 On 3 June 2013 18:04, wrote: > No, Go's intent is to minimise runtime surprises. It's not a runtime surprise to Go programmers, since no ordinary Go code runs in that note handler. There's a rather elaborate implementation to convert notes (or signals) into something acceptable to the rest of the Go runtime. It does as little as it can. --001a11c2443cb9c4e804de436efd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On 3 June 2013 18:04, <lucio@proxima.alt.za> wrote:
<= blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px= #ccc solid;padding-left:1ex"> No, Go's intent is to minimise runtime surprises. =C2=A0
It's not a runtime surprise to Go programmers, since no ordinar= y Go code runs in that note handler.
= There's a rather elaborate implementation to convert notes (or signals)= into something acceptable
to the rest of the Go runtime. It does as = little as it can.
--001a11c2443cb9c4e804de436efd--