Hello,

I wanted to reach out and see whether there is an interest in the fix for #34437 being included in the Go release notes. Someone I know was finally working through upgrading to Go 1.14 and ran in to some peculiar issues with their JSON being unmarshaled differently. Here is that commit on our side:

• golang/go@fb9af84#diff-429

Do we expect the following syntax to work?

julia> [Int, Float64, String, Bool] .<: Union{Int, String}
ERROR: syntax: space not allowed after ":" used for quoting

It works if you call <: as a broadcasted function:

julia> (<:).([Int, Float64, String, Bool], Union{Int, String})
4-element BitArray{1}:
 1
 0
 1
 0

Version info:

Julia Versio

1. https://vlang.io/play

Example ( JSON decoding/encoding ):

Returns:
You just found a bug. V can't compile this program, but it should. Please create a GitHub issue.

Solution: ?

2. https://vlang.io/docs

fn main() { age = 21 }

Using Run works perfectly.

But all other examples like Strings, ...

name := 'Bob' println('Hello, $name!') // $` is used for strin

Hi all! After working on it for 3 months, I'm excited to announce that the first draft of 《文言陰符：文言文編程入門》, Introduction to Programming in Wenyan is available! It is an introduction to wenyan-lang as well as programming in general, written completely in idiomatic Classical Chinese! Check it out!

You can either download an authentic-looking [PDF](https://g

Is there some way to differentiate between comments and (doxygen-like) documentation?

Typically code comments are

// foo
/* foo */

While doxygen and almost everything else uses the following:

/// foo
//! bar

/** foo */
/*! bar */

Being able to get two different metrics would be extremely helpful in assessing "quality of documentation"...

Thanks!

This is probably related to if not identical to #1687, but we at least need a better error message.

https://reasonml.github.io/try?reason=M4dwlgLgxgFgFARgNQIJQAIDeAod6A+6ATOgLwB86cqu6A9AFS0CGAJq+swHboCmAHhABOzdA3QQA9hJi90wCMyER0kgGYywwdFEkBbPby4QANPOmR0AI167D2hkzwM6tQgH0ylatgC+QA

switch(1+1) {
  | 2 => ()
  /*
  works
  */
  | _ => ()
}

switch(1+1) {
  | 2 => ()
  /

In the version deployed at http://play.witheve.com/#/examples/quickstart.eve the hover text for sidebar expand/collapse button is reversed. Look through the repo for the offending code but could not find it.

https://github.com/dart-lang/sdk/blob/master/docs/process/experimental-flags.md#flag-format-for-cli-based-tools

Our docs show:

dart --enable-experiment super-mixins

This format does not work on the VM. It should be:

dart --enable-experiment=super-mixins

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/

Red/System []
s2: declare struct! [
   a   [integer!]
   b   [c-string!]
   c   [struct! [d [integer!] e [float!]] value]
]
probe size? s2

Taken from https://static.red-lang.org/red-system-specs.html#section-4.7.2
Says:

Compiling to native code...
*** Red/System Compiler Internal Error: Script Error : last expected series argument of type: series port tuple
*** Where: for

It now defaults to clang instead of gcc.

More users will probably have gcc rather than clang.
We could document how to set in the installation instructions.

Description

Right now there is no documentation on how to run tests for this repository, It would be great if a simple document/ section of the readme could outline how to run the tests locally

Why

this would make it faster for people to dig into the compiler and understand it by observing the effects their changes have on tests. It would also support good, tested contributions by ma

Someone asked on IRC how if Elvish supported vi mode editing. I couldn't find any mention in the documentation and greping the source didn't return any promising results. It turns out that doing

edit:insert:binding[Ctrl-'['] = $edit:command:start~

will enable a very limited vi editing mode. See also #730 for why the features are currently limited. The currently support vi commands

So currently the doc for EReg.matched says this:

The index n corresponds to the n-th set of parentheses in the pattern
of this EReg. If no such sub-group exists, the result is unspecified.

But it's not immediately clear what "no such sub-group exists" means exactly. I assume it means that the group was not defined in the regex. But it's a bit confusing in case the group was define

• Have you checked the guidelines in our Contributing document?

Description

Hola, tengo un problema con esta función, la copie y pegue en mi proyecto sin descargar toda la librería pero su retorno no es correcto. ejemplo

number_format(1029,2,',','.');

//resultado 1.0.2.9,00

Currently, when doing a push, UCM creates messages like 'Sync branch ' which is not super informative. It is useful to know the namespace hash but it would be nice to know the diff from the previous version as well.

The message comes from here:

https://github.com/unisonweb/unison/blob/master/parser-typechecker/src/Unison/Codebase/Editor/Git.hs#L146-L151

But actually, rig

Here I have another suggestion, this time about our Gravity's CLI. I come up with this list of improvements which I think should benefit the project:

• If no arguments passed it should display help section instead of opening REPL
• To open REPL add a new flag for example gravity --repl
• gravity new [project] - a new simple command to create new project. (A wizard which helps with co

Motivation

In supercollider/supercollider#4572 we discussed the need for better documentation on when collection functions test on equality vs identity. For instance, SequenceableCollection:indexOf tests on identity, but you wouldn't know it f

Really nice project.

Writing in coconut files, you lose all the IDE integrations for Python. For example, I use VSCode and all the intellicode and hints of course doesn't work for cocount.

I am not too familiar but perhaps theres needs to be a separate language server or maybe you could leverage the existing Python integrations. Either way, better IDE integration wo