ameliorate / buildengine5 Goto Github PK

This launcher should accept command line arguments to either open a server or connect to one. It should also demonstrate the full capabilities of the engine and the correctness of its code.

This could probably borrow some ideas from duck-typing, maybe.

The difference between a trait and an event would be that an event is global: you can't choose which implementation is used, while with a trait, you can choose.

One place this would be used is the networking packet hooks. This would be where you could put some sort of anti-cheat subsystem.

Probably a few macros may be needed.

Also, a big question that would save a bit of code is if &mut EventLoopImpl is functionally equivalent to the current EventLoopImplMutRef.

• Move from using trait objects to monomorphization.
• Remove most of the "cruft" that has built up from learning things, and organizational changes.

The future of Github is uncertain. Also Gitlab looks kinda nice.

Since it is a single value, updated multiple times concurrently, it is a possibility that tests may be erroneously passing. This could be fixed using multiple TEST_VALs or a map of some kind.

---- net::test::client_server_send stdout ----
    thread 'net::test::client_server_send' panicked at 'old_test_val < new_test_val, old_test_val: 0, new_test_val: 0', src/net/test.rs:59

It seems to be that the test packet is not sending. Further debugging is needed to determine if it is just the test packet or all packets.

Currently an error does not include the file/module from which it occurred. It would be useful to have this feature.

A lot of the methods in net just panic when coming across io errors. It would require a large number of crash reports to determine all the errors that possible.

It should preferable be capable of outputting markdown, so that the docs could be merged with the current rustdocs.

Files should be loaded by the launcher, but processed by the engine.

Most of the netcode is reusable in other projects, and there currently is no high level networking library in rust.

Netcode as it stands is terribad, has bad test coverage, and can't be helped. I'd also like to try to scrap mio. It alone is the sole cause of most of the outdated crates when I run cargo outdated.

Should succeed when all of the requirements of Networking -- 0.1.0 are completed.

Almost everything is in no order at all.

In the future, I'd like for there to be both user facing errors, with an explanation of how to fix it, and developer errors, explaining exactly what went wrong in the code. This would require some system of errors more complicated with panic!'s using strings.