Bug report

The following code causes an ICE:

fn main() {
    print!("\r¡{}");
}

As far as I can tell:

• Any number of characters can be inserted between \r and ¡ and the error will still happen.
• ¡ can be replaced with any unicode character and the error will still happen.
• No escape sequences other than \r cause the error.

The error is reproducible on the stable or nightl

Description

Add proseWrap: never to the prettier config options for markdown files in the docs/ directory (or all files if so inclined). Also add it to the prettier config of gatsby-i18n-source

Motivation

The [Translation Style Guide](https://www.gatsbyjs.org/contributing/translation/style-guide/#use-so

Feature Request

This means that it should be enabled by default in @babel/parser 🎉

It should be done similarly to this commit: babel/babel@c3388ea

1. Remove all the this.hasPlugin and `this.expec

#4001 🐛 bug report

Applying @parcel/transformer-raw to a file causes it to be renamed as if it was an asset rather than an entry.

🎛 Configuration (.babelrc, package.json, cli command)

// .parcelrc
{
	"extends": ["@parcel/config-default"],
	"transforms": {
		"*.json": ["@parcel/transformer-raw"],
	}
}

// entry.json
{}

$ parcel build entry.json

Describe the bug
If you define an on:change attribute before a bind:value attribute, the on:change handler doesn't work.

To Reproduce
This REPL shows how it should work.
https://svelte.dev/repl/b2dfff7844614d9e8ce07f8d41fc3086?version=3.20.1

Swap lines 44 and 45 around. The input boxes will stop updating when the select is changed.

Expected behavior
It shouldn't matter whe

Marked version: 0.7.0

• December 2017: Should we perform a miracle?
• February 2018: MarkedJS Organization is opened. Core team and roadmap established.

This is a community effort. The core team is primarily here for c

V version: V 0.1.25 c12985d
OS: macOS 10.15

What did you do?

grepping in the source i found all those [..] attributes used or documented. its a bit confusing to understand what are they for and how/when to use them. so it will be good to have some tests and document them in doc/attributes.md

Also it is possible to define custom attributes like in python or c# ?

type

Hello, could we somehow document #522 / provide a better error message? I've spent waaaaay too much time trying to solve the issue before finding the already existing solution:/

Even better - fix it, instead of a work-around?

Thanks!

On OSX, rather than using ctrl-C (copy) or ctrl-V (paste) the standard is to use command-C/command-V, but neither of these bindings work within the app.

The documentation for reflect.DeepEqual makes no mention of panic'ing: https://golang.org/pkg/reflect/#DeepEqual

In this example it panics:

println(fmt.Sprintf("fieldVal %T %v", fieldVal, fieldVal))
println(fmt.Sprintf("Zero %T %v", reflect.Zero(reflect.TypeOf(fieldVal)).Interface(), reflect.Zero(reflect.TypeOf(fieldVal)).Interface()))
reflect.DeepEqual(fieldVal, reflect.Zero(reflect.T

sizeof doesn't work for types that store Atomics. This would be useful to size the memory buffer for thread-safe memory allocators with what is left from the synchronization primitives.

import std/atomics

type
  Node = ptr object
    # works
    next: Atomic[pointer]

  MyChannel = object
    # type not defined completely
    back: Atomic[ptr int]

static:
  echo sizeof(N

Currently 1000_000.1234_1234 tokenized as 1000 but should read as 1000000.12341234

Describe the feature

/*! Copyright (c) 2020 Foo */ should not be removed when minifying

Babel plugin or link to the feature description

https://stackoverflow.com/questions/11248363/the-purpose-of-starting-an-initial-comment-with-in-javascript-and-css-files

Is your feature request related to a problem? Please describe.
No.

Describe the solution you'd like
I'd like the source code to be automatically clang-formatted according to my settings anytime the code is compiled. That is, don't require me to use the contextual menu or keyboard shortcut to format the code. Just auto-format it; just like the code is auto-compiled too.

Well, ther

Currently there is no documentation when I compile a Fat Framework for iOS, even when I put documentation in the common code. I'm not entirely sure where it should go, perhaps in the ObjC headers?

Using elm 0.19.0 or 0.19.1-beta-1, a package documentation with a @docs not starting a line is accepted by the compiler but not parsed correctly by https://github.com/elm/project-metadata-utils/blob/1d43c1a660c4f7dca9f14e64a050ac3971141221/src/Elm/Docs.elm#L280.

For example:
https://github.com/carpe/elm-data/blob/90456b6a3454e75aa9d103be07d98df822d4c312/src/ElmData/AuthConfig.elm#L6
resu

Depends on #4728 and #4729

• how it works
• why to do it / it creates a "seam" between blocking and async code
• examples of runtime safety checks associated with this feature

With v0.6 adding quantization support, I think it is good time to add documentation on our quantization story.

There have been many questions on the forum, some of which are listed at the bottom. I myself have recently become interested in the topic, but I'm having hard time digging through the forum, github issues, PRs etc.

It would be great if we could add an end to end quantization usag

Eclipse OMR is a C/C++ toolkit for building language runtimes. OMR has a high level JIT compilation library called JitBuilder, which is built on OMR's more general compilation framework. We also have a demo VM called [Base9](https://github.com/b9org/

https://caml.inria.fr/pub/docs/manual-ocaml/manual042.html

We can do this for Belt.Map as well

Problem

walt-cli package when linking multiple .walt files together can "wrap" the modules in a stand-alone JS module. The resulting module is too large because it serialized the dependency tree with the AST information encoded directly into the output, resulting in a massive amount of js.

Encoding the dependencies into the file is done to ensure the module can be used stand-alone in br

When using asciidoctot.js with object-hash, object-hash will throw error during hashing Object.__proto__.constructor, because it finds the $$base_module property on Object.__proto__.constructor, then try to hash it.

The $$base_module property on Object.__proto__.constructor is enumerable:

![image](https://user-images.githubusercontent.co

I quote from a recent conversation in red/help
Every built-in function has a specification which tells you what the (type of) result is. Or, at least, it SHOULD have this. The docstring of print, e.g., does not tell you its result is unset. Admittedly that might be added.
If HELP <built-in> would always show the type of result, problems such as with print could be avoided for new users.

See scala-js/scala-js#3874 (comment)