Cyclops 4 HPC is the purpose built stack to support large HPC centers with resource accounting and billing of cluster as well as cloud resources.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
Diego Martin 0ea0435502 [U] Sync of latest codebase 3 years ago
..
.gitignore [U] Sync of latest codebase 3 years ago
.travis.yml [U] Sync of latest codebase 3 years ago
LICENSE.md [U] Sync of latest codebase 3 years ago
README.md [U] Sync of latest codebase 3 years ago
bom.go [U] Sync of latest codebase 3 years ago
discard_go14.go [U] Sync of latest codebase 3 years ago
discard_go15.go [U] Sync of latest codebase 3 years ago
go.mod [U] Sync of latest codebase 3 years ago
go.sum [U] Sync of latest codebase 3 years ago

README.md

bom

strip UTF-8 byte order marks

GoDoc Build Status (Linux) Build status (Windows) License Coverage Status GoReportCard

The bom package provides a convenient way to strip UTF-8 byte order marks (BOM) from the beginning of a byte slice or an io.Reader.

The Unicode Standard defines UTF-8 byte order marks as the byte sequence 0xEF,0xBB,0xBF, but neither requires nor recommends their use. The Go standard library provides no support for UTF-8 byte order marks, and it looks like it never will. To quote Andy Balholm in the discussion on this issue at https://groups.google.com/forum/#!topic/golang-nuts/OToNIPdfkks

The Go team includes the original designers of UTF-8, and they consider BOMs an aBOMination. They are reluctant to do anything to make life easier for people who use BOMs. :-)

(Although they did make the compiler accept source files with BOMs, if I remember right.)

In the same discussion thread another participant makes the comment that it should not be difficult to write an io.Reader that eats the BOM.

It isn't difficult, and here is one simple implementation.