Dilum Aluthge comments

Results 688 comments of


                                            Dilum Aluthge

Warn when activating manifest that was resolved in a different julia version

> Also, I've been thinking that Pkg should use fewer `@error`'s and instead format the error messages using `printpkgstyle`? The clash of the two formatting modes is a little inelegant....

Improve the "empty intersection" error message

In addition, we could change the text `project compatibility` to `project compatibility (e.g. [compat] entry)`.

register NNlibCUDA as a subpackage of NNlib

@JuliaRegistrator register() subdir=lib/NNlibCUDA

register NNlibCUDA as a subpackage of NNlib

Yeah no worries at all! We can merge it manually in 3 days.

register NNlibCUDA as a subpackage of NNlib

> there is no problem in pulling out at any moment anyway As I've mentioned elsewhere, moving the location of a subdirectory package is nontrivial. You have to make sure...

register NNlibCUDA as a subpackage of NNlib

Idk, I've never done it myself, but here's one data point: SnoopCompileBot was originally a subdirectory package. At one point, the maintainer wanted to move it to its own repo....

Alternative to Windows Store for Windows - an msi installer for juliaup

@ViralBShah Can you give this approach a try?

`Pkg.Operations.install_archive`: when unpacking the archive, always rethrow the caught exception unless it is a `ProcessFailedException`

@StefanKarpinski @KristofferC Does this look correct? I figure it would be best if we only catch the narrowest necessary set of exceptions.

Print a hint suggesting `shared = true` if the user does `Pkg.activate("@foo")`

Alright, `Pkg.activate` and `] activate` now use the same parsing logic, namely: 1. Determine if it looks like a shared environment by doing `first(path) == '@'`. 2. If it looks...

softmax kernel

@SimonDanisch @MikeInnes What was the conclusion regarding this PR?