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

Rewrite in C++ so we can rewrite in rust. #4

Closed
Gammer0909 opened this issue Nov 3, 2023 · 7 comments
Closed

Rewrite in C++ so we can rewrite in rust. #4

Gammer0909 opened this issue Nov 3, 2023 · 7 comments

Comments

@Gammer0909
Copy link

Normally this is the point where someone says

Rewrite in Rust so it can be blazingly fast and safe!!

But it's already written in Rust, we can't rewrite it in Rust. Therefore, I am proposing we rewrite it in C++, so we can then rewrite it in Rust.

When this issue gets cleared I shall begin a C++ rewrite

@owofied
Copy link

owofied commented Nov 3, 2023

Because of C++, the project will be no longer maintained because the maintainer would be found dead with his legs blown off, so I would rewrite it in javascript first and then in rust

@Gammer0909
Copy link
Author

Because of C++, the project is no longer maintained because the maintainer would be found dead with his legs blown off, so I would rewrite it in javascript first and then in rust

Well we need it to be in C++, because the person asking for a Rust rewrite always complains

We shouldn't use C++ because Rust is memory safe

Therefore, we have to have it in C++. Also, half the project is already written in JavaScript.

@Shlok-Bhakta
Copy link

I agree that we should rewrite this in JavaScript so we can use electron. Then we rewrite this in rust for true blazingly fast code.

Maybe even embed c++ using only features from c into the JavaScript for extra stuff to rewrite

@Linker-123
Copy link

You should sprinkle some huge C++ templates and complex inheritance. Additionally let's respect C by only using malloc.

@Linker-123
Copy link

Please make sure to randomly try and free a reference from time to time, additionally add a macro for true so that luck can decide how the program will work.

Proposed solution:

#define true (time(nullptr) % 86400 != 0)

@face-hh
Copy link
Owner

face-hh commented Nov 4, 2023

😂

@face-hh face-hh closed this as not planned Won't fix, can't repro, duplicate, stale Nov 4, 2023
@Gammer0909
Copy link
Author

Dang this issue got a lot more support than I thought. Are we clear for a rewrite?

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

No branches or pull requests

5 participants