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

Ankit Shah and I are trying to use Gen to support a project and would love the addition of a dirichlet distribution

The documentation states that

Plots offers shorthands like png(fn), etc.

However, it appears that png() is the only convenience function that is exported, which is confusing for users trying to do pdf(fn).

I assume the intention is to export these functions? If not, having to

From the readme, section on Package status:

Currently, METADATA has a tag system but not all package authors use it, making it harder for lay users to know if the package maintenance is active or not.

I don't know how to do this, please add a link, or small tutorial. I'd like to do it.

The following pkgdown R library allows generating a doc site based on GitHub repo information (e.g. the README.md, developers etc). Wondering whether we can do something similar with Turing sub-modules, particularly build a page from the README.md file and release notes.

https://pkgdown.r-lib.org/

In particular, the default rotation speed is not very good. Could we slow down the rotation speed by default? It is hard to interact otherwise.

I was trying to use the Julia: Execute Code Cell Command, but I didn't know what was the delimiter for a cell. Finally, I found it, but It would be nice to have a comment about it :).

Currently, the setup phase is documented properly, but a similar example of the teardown would be well appreciated as that quickly got lost when trying to work on some benchmarks I was working on recently. It wasn't obvious that my benchmark (specifically the teardown) was set up properly, and there wasn't a simple one-or-two liner in the docs that I could use to verify what I was doing was

The error I get when I click on a URL in the documentation:

Couldn't resolve URL @ref
Configuring paths to API docs in project settings might help
External documentation for Array

I had my Clion shortcut in C:\JuliaPro-1.1.1.1 folder.
![image](https://user-images.githubuser

Will error as it will try to do a reduction over an empty collection which is not allowed

Fix: early return if no code.

It seems like the documentation is outdated for vim and emas. The examples still suggest that one should handle a Dict as the last argument to the LanguangeServerInstance. However, it seems like this is a function now (error handler). Unfortunately, I don't know enough about the internals to update the documentation myself and make a PR, all I can tell is that the current documentation seems o

Would be really nice if julia-mode provided ability to edit docstrings using
markdown-mode. Not an elisp guy, and still a relatively new emacs user, so I'm
not sure exactly how this would work, but I thought I'd throw the suggestion out
there.

Maybe if I get some time, I'll take a look at how org-mode does it with src
blocks and see if I can duplicate that in julia-mode.

Currently we say things like "<8 TPU chips in 2x2x2 topology>", which is informative, but doesn't match Google terminology. We could try printing something like "<TPUv3-8 in 2x2 topology>". We don't get the chip kind information from the topology, but we could for now just determine it from the memory information.

add_element!(mesh, elid, eltype, connectivity)
Add an element into the mesh. ´elid´ is the element id, ´eltype´ is the type of the element and ´connectivity´ is the connectivity of the element.

At least eltype needs to be defined more precisely. I guess it's a symbol :Seg2, :Tri3 and so on.

There was recently some discussion on Stan Discourse that resulted in this PR in Stan and this PR in PyMC3. They make some changes to the NUTS criterion to handle a previously undiscovered case where the N

The BlueStyle conventions are great!

I was wondering if people would be interested in discussing adding some guidelines on when to use export and how that relates to the current section on using using and import. Additionally, it would be nice to clarify if how this guideline on

Is there no documentation or am I just missing something? I would like to create an animation that changes what object is being displayed over time. The animation demo wasn't helpful for this case.

We should make an additional documentation page, called "Example overview". In this page we list the examples (as bullet points). In each bullet point we explain what the user can learn by each example page.

Eg. from HK model they learn synchronous agent update. From COVID-19 they learn using arbitrary graphs and plotting on arbitrary graphs. etc.

Proposed Sections on POD Documentation,

• README.md: general description and instructions for POD.jl

• Documenter.jl

  • Introduction: General solver description
  • How to Use: Instruction of installing and using POD with an example
  • Choosing Solver: List of supported sub-solvers and directions on how to use them
  • Algorithm: Big-picture description and point to the paper
  • Expr

Test case:

# LATex in Documenter strings
  doc"""$\pi$"""
# ^^^^^^^^^^^^^^ string.quoted.other

Patch:

  strings:
    ...
    # Documenter string, tripple-quoted. Has special escaping and no string interpolation.
    - match: '\bdoc"""'
      push:
      - meta_scope: string.quoted.other.julia
      - match: (\\"|\\\\)
        scope: constant.character.escape.j