julia-language

round(Int, π) throws an error, for example.

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

As I understand, the LineString type allows the user to plot multiple disconnected lines in the same plot call. However, there is no documentation to reflect this. We should add some, and possibly consider adding documentation (in the docs of lines, surface, heatmap, etc.) about which types they accept. Possibly also a listing of convert_arguments signatures which are applicable to each

Hi! It would be great if the grid function errors when the heights and widths are not correctly set — so the users can understand the incorrect behavior through the error messages. In the following example, we should throw an error if one of the values is zero or if the sum is greater than one. Also, the argument should allow PlotMeasures units as they create error messages that are difficult

Elevator Pitch

Right now Jupyter LSP show it's suggestions on every period. I'd like to have a feature that only generates the suggestions when a hotkey is pressed. (Shift Tab, etc)

Motivation

One of my users asked for the feature.

Design Ideas

I noticed it done here: https://github.com/JuliaIO/HDF5Plugins.jl/blob/main/Project.toml

I noticed in this package Blosc is commented out, for some reason (also not in the package above/main HDF5), not sure why, I don't really care if it's supported if the best format is support that I think is Zstd (seems also important for compatibility with main format):

https://github.com/JuliaIO/JLD2.jl

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.

In the readme maybe separate automatic forecast into auto_ets and auto_arima, adding an example for the last:

model = auto_arima(log_air_passengers; seasonal = 12)

And in documentation improve the automatic forecast section adding working examples of auto-arima. Saying that is possible to fix an integration order, play with the parameters...