From 6dca9ac791054ebcaf02362bd7e6ab00c18a4b7d Mon Sep 17 00:00:00 2001 From: Ian Lance Taylor Date: Tue, 29 Nov 2016 17:58:46 -0800 Subject: [PATCH] doc: add release notes for os and os/signal packages TBR=See https://golang.org/cl/33244 Updates #17929 Change-Id: I2e5b24fb0b110d833a8b73bccfbf399cb6e37ea2 Reviewed-on: https://go-review.googlesource.com/33681 Reviewed-by: Ian Lance Taylor --- doc/go1.8.html | 53 ++++++++++++++++++++++++++++++++++++++++++++++++++ doc/go1.8.txt | 9 --------- 2 files changed, 53 insertions(+), 9 deletions(-) diff --git a/doc/go1.8.html b/doc/go1.8.html index 88ba6bc0a30..dd6e9af2d86 100644 --- a/doc/go1.8.html +++ b/doc/go1.8.html @@ -1281,6 +1281,59 @@ pkg debug/pe, type StringTable []uint8 Executable returns the path name of the running executable.

+ +

+ An attempt to call a method on + an os.File that has + already been closed will now return the new error + value os.ErrClosed. + Previously it returned a system-specific error such + as syscall.EBADF. +

+ +

+ On Unix systems, os.Rename + will now return an error when used to rename a directory to an + existing empty directory. + Previously it would fail when renaming to a non-empty directory + but succeed when renaming to an empty directory. + This makes the behavior on Unix correspond to that on other systems. +

+ +

+ On Windows, long absolute paths are now transparently converted to + extended-length paths (paths that start with \\?\). + This permits the package to work with files whose path names are + longer than 260 characters. +

+ +

+ On Windows, os.IsExist + will now return true for the system + error ERROR_DIR_NOT_EMPTY. + This roughly corresponds to the existing handling of the Unix + error ENOTEMPTY. +

+ +

+ On Plan 9, files that are not served by #M will now + have ModeDevice set in + the value returned + by FileInfo.Mode. +

+ + + +
os/signal
+
+

+ In a Go library built with -buildmode=c-archive + or c-shared, when C code calls a Go function, + the SIGPIPE signal will be treated as usual for Go code. + In particular, when SIGPIPE is triggered by a write + to a closed Go network connection, it will not cause the program + to exit. +

diff --git a/doc/go1.8.txt b/doc/go1.8.txt index 7c61a4f91a4..800464dc1ef 100644 --- a/doc/go1.8.txt +++ b/doc/go1.8.txt @@ -82,15 +82,6 @@ go/types: match cmd/compile's alignment for complex64 (CL 31939) html/template: check "type" attribute in