Skip to content

merge from upstream (2019/10/09) #11

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 54 commits into from
Oct 9, 2019

Conversation

compnerd
Copy link
Member

@compnerd compnerd commented Oct 9, 2019

No description provided.

philipturnbull and others added 30 commits February 20, 2018 12:25
For empty documents, `->size` is zero so
`renderer.buffer->ptr[renderer.buffer->size - 1]` will cause an out-of-bounds
read. Empty buffers always point to the global `cmark_strbuf__initbuf` buffer
so we read `cmark_strbuf__initbuf[-1]`.
We currently discard fuzz test-cases that are empty but empty inputs are valid
markdown. This improves the fuzzing coverage slightly.
Allow the `width` parameter to be generated too so we get better fuzz-coverage.
to avoid unnecessary repetition.  Once we settle
whether a list item ends in a blank line, we don't
need to revisit this in considering parent list items.

See commonmark#284.
Use this to avoid unnecessary recursion in ends_with_blank_line.

Closes commonmark#284.
As with other static functions.
Keep track of the last position where a thematic break
failed to match on a line, to avoid rescanning unnecessarily.

See commonmark#284.
Check for empty buffer when rendering
Removes CMARK_OPT_SAFE from options.

Adds CMARK_OPT_UNSAFE, with the opposite meaning.
The new default behavior is to suppress raw HTML and
potentially dangerous links.  The CMARK_OPT_UNSAFE
option has to be set explicitly to prevent this.

--------------------------------------------------------
NOTE: This change will require modifications in
bindings for cmark and in most libraries and programs
that use cmark.
--------------------------------------------------------

Closes commonmark#239, commonmark#273.

Borrows heavily from @kivikakk's patch in github#123.
It is deprecated in CMake 3.0, the replacement is to set the
CXX_VISIBILITY_PRESET (or in our case C_VISIBILITY_PRESET) and
VISIBILITY_INLINES_HIDDEN properties of the target.

We're already setting them by setting the CMake variables anyway, so the
call can be removed.
It doesn't do anything; this is documented.
A link destination can't start with `<` unless it is
an angle-bracket link that also ends with `>`.

(If your URL really starts with `<`, URL-escape it.)
Fix cmake warning about CMP0048, again
jgm and others added 24 commits April 3, 2019 10:24
to conform with spec change.
For markdown content, e.g., in other contexts we want some
kind of escaping, not a literal newline.
URL-escape special characters when escape mode is URL,
and not otherwise.

Entity-escape control characters (< 0x20) in non-literal
escape modes.
A setext header line after a link reference should not
create a header, according to the spec.

See commonmark/commonmark-spec#395.
If CMARK_STATIC is on (default), link the executable with the static
library. This produces exactly the same result as compiling the library
sources again and linking with the object files.

If CMARK_STATIC is off, link the executable with the shared library.
This wasn't supported before and should be the preferred way to
package cmark on Linux distros.

Building only a shared library and a statically linked executable
isn't supported anymore but this doesn't seem useful.
Link executable with static or shared library
Add built cmark.exe as an AppVeyor artifact
cmake adds `-rdynamic` on linux, even for static builds.
This commit removes it for linux builds by resetting
`CMAKE_SHARED_LIBRARY_LINK_C_FLAGS`.
A code span can have more than its two surrounding ones, like ` `` `.
@compnerd
Copy link
Member Author

compnerd commented Oct 9, 2019

CC: @akyrtzi @shahmishal

@akyrtzi akyrtzi merged commit 4c3a7ae into swiftlang:master Oct 9, 2019
@compnerd compnerd deleted the merge-2019-10-09 branch October 9, 2019 20:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.