Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FemtoCleaner for julia 1 #114

Open
wants to merge 13 commits into
base: master
Choose a base branch
from
Open

Conversation

aminya
Copy link

@aminya aminya commented Aug 14, 2019

Needs help.

Fix AbstractTrees download command for local run
Fix running FemtoCleaner.cleanrepo command
Added Julia 6.4 download link
Fixed non-working URLs
Brought local running in Readme upfront
@aminya aminya changed the title Amin julia1 FemtoCleaner for julia 1 Aug 14, 2019
Update README.md
Update .travis.yml
Create Project.toml
@XVilka
Copy link

XVilka commented Aug 20, 2019

1.19s$ julia -e ' Pkg.clone("https://github.com/aminya/Deprecations.jl"); Pkg.clone(pwd()); Pkg.build("FemtoCleaner"); Pkg.checkout("AbstractTrees"); import JSON; for (pkg, version) in JSON.parse(readstring("dependencies.json")) LibGit2.with(LibGit2.GitRepo, Pkg.dir(pkg)) do deprepo LibGit2.checkout!(deprepo, version) end; Pkg.pin(pkg); end; Pkg.resolve(); Pkg.test("FemtoCleaner"; coverage=true) '

ERROR: UndefVarError: Pkg not defined

Stacktrace:

 [1] top-level scope at none:0

The command "julia -e ' Pkg.clone("https://github.com/aminya/Deprecations.jl"); Pkg.clone(pwd()); Pkg.build("FemtoCleaner"); Pkg.checkout("AbstractTrees"); import JSON; for (pkg, version) in JSON.parse(readstring("dependencies.json")) LibGit2.with(LibGit2.GitRepo, Pkg.dir(pkg)) do deprepo LibGit2.checkout!(deprepo, version) end; Pkg.pin(pkg); end; Pkg.resolve(); Pkg.test("FemtoCleaner"; coverage=true) '" exited with 1.

Failed Travis

@aminya
Copy link
Author

aminya commented Aug 20, 2019

I abandoned updating this. It is beyond my experience with Julia. Someone should know old syntaxes and then update this. The developers themselves should update this

@logankilpatrick
Copy link

So the issue is that the syntax of the repo itself needs to be updated?

@aminya
Copy link
Author

aminya commented Sep 13, 2019

Yes the FemtoCleaner/Deprecations should be written in Julia 1. Also, we need to address changes after Julia 0.6.4 in Deprecations so FemtoCleaner uses them.
If we could do this, there are numerous packages to revive (https://discourse.julialang.org/t/ann-plans-for-removing-packages-that-do-not-yet-support-1-0-from-the-general-registry/28003 )

@logankilpatrick
Copy link

logankilpatrick commented Sep 13, 2019 via email

@aminya
Copy link
Author

aminya commented Sep 13, 2019

Can FemtoCleaner clean itself?! Best, Logan Kilpatrick

On Sep 12, 2019, at 9:42 PM, Amin Yahyaabadi @.***> wrote: Yes the FemtoCleaner/Deprecations should be written in Julia 1. Also, we need to address changes after Julia 0.6.4 in Deprecations so FemtoCleaner uses them. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

I have already done this in this PR. But that is not enough because Deprecations doesn't address the changes after Julia 0.6.4

@XVilka
Copy link

XVilka commented Oct 17, 2019

Too bad actual repository owners keep silence on this issue.

@logankilpatrick
Copy link

logankilpatrick commented Oct 17, 2019 via email

@aminya
Copy link
Author

aminya commented Nov 28, 2019

If anyone wants to work on this, they responded to my old issue:

julia-vscode/CSTParser.jl#102

I am trying to upgrade Deprecations.jl for FemtoCleaner. In Deprecations code CSTParser.BinarySyntaxOpCall is used a lot like here.

I found its definition here.

What has happened to this in recent versions?

Answer:

Dedicated expression datatypes (e.g. BinarySyntaxOpCall, UnaryOpCall, etc.) were replaced by a single expression type (EXPR). The 'type' of expressions are now stored in the .typ field which should be accessed using CSTParser.typof(x::EXPR).

The change was made for increasing parsing speed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants