juliadocs / julia-cheat-sheet Goto Github PK

Hi,

for a recent crash course, I created this fork and added syntax highlighting:
https://steffenpl.github.io/Julia-Cheat-Sheet/

Shall I create a pull request?

PS: I also added content to the cheat sheet, but I guess that is another discussion.

Hello, nice cheat sheet. It would be nice to have a pdf and png files for download

A test suite would be a great improvement to catch both typos and also, as Julia changes, ensure we're always up to date. Probably makes sense to wait for #39, or integrate with that effort.

It was mentioned on slack that produce and consume are deprecated.

Hi I see on your doc: https://juliadocs.github.io/Julia-Cheat-Sheet/ and I've seen in code from 2017 that unshift! is used however if I start up a julia terminal on my machine version, julia 1.0 unshift! is not defined.

Could we get this in PDF by chance?

you may get a little more traffic in coming days, as I put your beautiful cheatsheet on the julia community pages.

Quoting from the cheat sheet:

@macroname(ex1, ex2, ...) or
@macroname(ex1, ex2, ...)

I assume the second line should be without parens?

Now that we've had so many people do AMAZING work translating this, it occurs to me we have a new problem: how do we manage changes to the cheat-sheet? Most of us do NOT know Spanish, Portuguese, and Mandarin, so aren't suited to making changes in all translations. But we also want to allow people to update content.

Suggestions?

It should be removed.

Getting a 404 for cheat-sheet?

This is a helpful Julia overview! I noticed in Characters-and-strings.md, under "Any UTF character", that 8-digit HEX '\uXXXXXXXX' should actually be '\UXXXXXXXX' (capital U).

[source]

Organização de tradução

• Indique qual arquivo você irá traduzir antes de começar para que ninguém duplique o esforço.
• Abra um Pull Request com sua tradução, colocando [br] no cabeçalho.
• alguém deve verificar o que você fez, comentar possíveis mudanças, e aceitar seu PR.

Se você puder ser revisor, avise.

O que precisa ser feito:

• Revisar #48, porque foi aceito sem ler
• Portar #46 e #45
• _data/blocks.yml (add br entry separately)
• Arrays.md (#48)
• Basics.md (#48)
• Characters-and-strings.md (#61)
• Collection-functions.md
• Control-flow-and-loops.md (#57)
• DataFrames.md (#52)
• Dictionaries.md (#75)
• Exceptions.md (#68)
• Expressions.md (#66)
• Functions.md (#55)
• IDEs-Editors-and-Plugins.md
• IO.md (#64)
• Introspection-and-reflection.md (#53)
• Linear-Algebra.md (#59)
• Macros.md (#70)
• Missing-and-Nothing.md (#54)
• Modules.md (#77)
• Naming-Conventions.md (#67)
• Noteworthy-packages-and-projects.md
• Numbers.md (#58)
• Operators.md (#56)
• Package-management.md
• Parallel-Computing.md
• Performance-tips.md
• Random-Numbers.md (#65)
• Resources.md
• Sets.md (#51)
• Standard-libraries.md (#60)
• The-shell-aka-REPL.md
• Types.md (#76)
• Videos.md (#62)
• What-is.md

I'm not fully up to date on what all has changed in 1.0, but wanted to start a list of things to update.

• Add section on missing types (and remove from Data Frames)
• Update Package Management section for Pkg3
• Add named tuples
• Noteworthy packages and projects needs a big update. I would add more of the "families": JuliaGraphs, JuliaOpt, etc.
• Performance tips are mostly out of date I think
• Add JuliaCon 2018 to videos, as well as videos on julialang
• Maybe update the aesthetic to be a little more modern than current purple-to-blue color fade in headers?
• Add section on REPL tricks?

I'm sure there are more that insiders will know...

A

Right now things are a bit of a jumble. I think after @abelsiqueira does the re-org, we should split things into something like:

• Basic Functionality
• Standard Library Functionality
• Packages
• Writing Modules
• Performance
• Additional Resources

Hey, to keep up with the conventions of GitHub, can we transition this repo from master to main?

dot(a, b) == sum(a .* w) should be dot(a, b) == sum(a .* b)

I'm preparing a workshop on open source and collaboration for Hacktoberfest and translating this cheat sheet would be a very fine exercise for a group of people.
To that end, I'm making a few modifications on a separate package:

• Use jekyll;
• Break index.html to several files (one for each box); and
• Convert each box from HTML to Markdown whenever possible.

Is this process of interest to the package? I can open a PR with the modifications above.

Please add a section with each of the functions in the Standard Library listed under or with the library to use to get such.

So, I would be listed under the LinearAlgeba library, and so forth.

collect((df[:col], 1)), do you mean collect(Missings.replace(df.:col, 1)) ?

it produces the error in julia 0.5. It probably supossed to be Int('J') == 74

mean(A,1)
should be:
mean(A,dims=1)

Furthermore, to use mean now you should first do:
using Statistics

When will this cheatsheet be updated to Julia 1.6?

Hi,
I know that NaN == NaN returns false, while isequal(NaN, NaN) returns true.
What is meant by not(!) NaN == NaN in the line transcribed in the title of this issue?
Many thanks for your amazing cheatsheet.
Regards,
Rodolfo

The URL on line 1 from Package-management.md ("Packages must be registered before they are visible to the package manager.") points to a package server.

Shouldn't it point to somewhere like this or this?

Lines don't wrap and get cut off. (You probably already know this, sorry)

Julia has an LLVM-based JIT compiler that allows it to match the performance of languages such as C and FORTRAN without the hassle of low-level code. Because the code is compiled on the fly you can run (bits of) code in a shell or REPL, which is part of the recommended workflow.

This link in 'workflow' is wrong now.

Currently says for julia 0.6

sizehint should be replaced by sizehint!, if I am not mistaken - as the Cheat Sheet refers to Julia 1.0.

In "Reshape from wide to long format''

stack(df, [1:n; ])
stack(df, [:col1, :col2, ...]
melt(df, [:col1, :col2]) [

Should the second stack be

stack(df, [:col1, :col2, ...])

And is there an extra bracket in melt, so should it be

melt(df, [:col1, :col2]) 

This Cheat Sheet is cool. I think it could be updated a bit.

@mortenpi @fredrikekre I'm happy to help out... 😂

Is it work keeping Pkg.installed() in the cheat sheet?

julia> Pkg.installed()
┌ Warning: Pkg.installed() is deprecated
└ @ Pkg C:\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.6\Pkg\src\Pkg.jl:566
Dict{String, VersionNumber} with 14 entries:
  "CSV"               => v"0.8.5"
  "Distributions"     => v"0.24.18"
  "TemporalGPs"       => v"0.5.11"
  "ParameterHandling" => v"0.3.2"
  "Interpolations"    => v"0.13.2"
  "Optim"             => v"1.3.0"
  "HTTP"              => v"0.9.10"
  "InfiniteOpt"       => v"0.4.0"
  "AbstractGPs"       => v"0.3.5"
  "Ipopt"             => v"0.6.5"
  "KernelFunctions"   => v"0.10.5"
  "Plots"             => v"1.16.5"
  "Zygote"            => v"0.6.12"
  "DataFrames"        => v"1.1.1"

There's a small typo in the Arrays section:
Select subarray from m to n | arr[n:m]
This should be of course:
Select subarray from m to n | arr[m:n]
Thanks for fixing this. Or should I do pull request?

Hi, thanks for the great cheat sheet!

One of the performance tips is ”devectorizing does not improve performance “
I guess it should be “vectorizing does not improve performance “?