A recent PR (#1180) raised awareness that the first page for many new library users is its docs.rs page, generated from the crate root documentation and not the extensive Readme. While moving all of the documentation, as proposed, felt like too broad, nevertheless the following discussion was quite constructive in how the overall structure could be improved. I'll quote relevant portions on what

Per [Section 3.2 of RFC4648], the padding on Base64 URL-safe codec is actually optional. [RFC7636] is a concrete example where a padless encoding is required (as explicitly stated in [Section 3]). Any chance for supporting padless Base64Url encoding out-of-the-box in scodec? This way, manual workarounds (e.g., ByteVector(bytes).toBase64(Base64Url).takeWhile(_ != '=')) would be eliminated.

In the documentation built from master branch, there are two examples with missing thumbnails. These were imported from Nistats, and they are missing there as well.

We need to fix this before rolling out the next Nilearn stable.

The two examples are:

9.5.2. Example of a events.tsv file generation: the neurospin/localizer events
04_glm/first-level-models-write-events-file.py

9.8.9. D

I got this error in go version go1.11beta2 using github.com/go-pg/pg
Run ok back then, but after update this error show up
src/github.com/segmentio/encoding/json/reflect_optimize.go:15:6: missing function body

TL;DR: metaflac should support outputting to a different file, like vorbiscomment(1).

Background: I have created a music compilation system which works kinda like a software build system. When possible, it encodes and tags in different steps so that a mere tag change doesn't result in the reencoding of the entire library.

Here are the bytes produced (valid).

dc 00 11 91 cf 05 88 12 52 88 c2 00 0a 90 95 91 cf 01 ad fd 36 26 40 00 00 d9 22 61 5f 63 35 65 64 63 37 31 61 66 66 37 65 33 63 35 39 61 64 31 36 31 37 32 64 31 37 66 31 35 66 38 39 c2 cd 04 d2 aa 6a 6b 63 63 6c 65 6d 65 6e 73 91 cf 04 43 f6 43 ab c2 00 01 da 02 4a 2a 2a 57 65 6c 63 6f 6d 65 20 74 6f 20 74 68 65 20 6c 61 6c 61 20 77 6f 72 6c 64 20 44 6

I ran Jazzy locally on Serpent, and it looks like the documentation percentage is not very high. This is about documentation for functions that the users don't actually access, but still, for completeness and quality, we should document those too.

This looks like it could be a very useful library for my use case, but the two very short examples provided give no insight into how I can use the module to extract functions from a .wasm file. Could you provide some kind of documentation for the module's methods, classes and class methods, etc. along with more comprehensive examples, so that we don't have to sift through the source code to figure

The website seems to reflect API changes in 0.6 but no tag exists. Is 0.6 still in progress or is the release tag missing?