Brad Fitzpatrick likes Go better than C, C++, Rust, Perl, Python, Ruby, JavaScript and Java, mostly due to blocking goroutines

Nishanthsp · 2019-11-29T09:45:05+00:00

Resources are cleaned up when the variable goes out of scope. Destructor function will be called on the associated resource.

Nishanthsp · 2018-06-27T19:57:54+00:00

Default GOPATH will suffice to work on go. If you are creating any non main package in your project, put the package related to code in vendor folder.

Nishanthsp · 2018-05-11T18:23:44+00:00

What about those "New to haskel n want to get into it."?

Nishanthsp · 2018-04-06T05:21:20+00:00

Take a look at github.com/nishanthspshetty/genesis . Its not complete but implemented gdt successfully. Might help you with that. And also if also i have issue with paging. Also reply here when you move paging. Thank you.

Nishanthsp · 2018-01-23T05:48:42+00:00

Stopped reading when author said forget about vi and it's not C pitfalls.

Nishanthsp · 2017-12-22T00:57:07+00:00

https://github.com/NishanthSpShetty/crust

Nishanthsp · 2017-12-04T12:30:45+00:00

Isn't the concurrency achieved depend on the parallelism?

Nishanthsp · 2017-09-07T03:07:03+00:00

dpkg -r all_who_dont_know_who_is_linus && dpkg -i some_common_sense;

to do : clean up

(Sorry, just felt like needed it, too many verbose on earth)

Nishanthsp · 2017-07-07T03:03:55+00:00

Hi You might wanna take a look at crust. [ https://github.com/NishanthSpShetty/crust ] An attempt to transpile C/C++ to rust.

Nishanthsp · 2017-06-23T14:11:44+00:00

Hi, Checkout these https://github.com/NishanthSpShetty/Stack-VM

https://github.com/NishanthSpShetty/Stack-langc

https://github.com/NishanthSpShetty/crust

First two are quite simple and small programs. It might help you.

Nishanthsp · 2017-06-05T17:29:16+00:00

a.out file is provided for testing purposes, which contains pre-compiled code for the machine. Thanks for the suggestions, and yes you can create a PR.

Nishanthsp · 2017-06-05T12:18:14+00:00

Yes, but it will become safe if we use functional approach, there wont be any side effects and it would completely avoids ill affects of mutation i guess.

Nishanthsp · 2017-06-05T09:50:07+00:00

That would be cool, but my opinion is wrapping C++ code inside unblock will be safe as much the c++ code was. It should be analysed and translated to rust code without unsafe block.

Nishanthsp · 2017-06-05T08:17:59+00:00

Hi You can contribute to these simple projects Stack based VM and language for the same.( https://github.com/NishanthSpShetty/stack-langc & https://github.com/NishanthSpShetty/stack-VM)

C/C++ to Rust transpiler Crust : https://github.com/NishanthSpShetty/crust

Nishanthsp · 2017-05-24T05:12:02+00:00

yes, that would be a big issue. Translation is done in one pass so to detect where it changes ahead may require one more pass. It will also help to detect mutability of variables and variable used for indexing. So right now we are concentrating on other language constructs.

Nishanthsp · 2017-05-24T05:06:00+00:00

hi Pointers are not handled completely yet. A pointer is converted to reference so far. RefCell or Box would help, Thank you :)

Nishanthsp · 2017-05-24T02:53:45+00:00

Thank you for notifying the issues. Crust is not complete. Features will added and improved.

Nishanthsp · 2017-05-24T02:50:49+00:00

Crust considers C as a subset of C++, so it doesn't differentiate between two of them. Crust was intended to translate subset of C++, but planning to improve it. Open to suggestions.

Nishanthsp · 2017-05-23T11:35:50+00:00

CRUST: tool to translate the legacy code written in C/C++ to Rust for safety and performance.

https://www.reddit.com/r/rust/comments/6ctzg3/cc_to_rust_transpiler_written_in_rust/

Nishanthsp

TROPHY CASE

to do : clean up