Now think, patents are similar things but for with more money. And imagine if someone else had similar idea and made slightly similar website you go sue them coz you had the idea first.
Those topics seems a little advanced for a Linux user without cyber security knowledge though. I personally don't understand any of them lol. I know what hardening is, what CVEs are; but except for few anecdotes like the logj4, xz, etc, I don't think I'd know enough to talk about the cyber security side of linux.
I was thinking more along the side of daily life things. Like how programmer like linux because it's easier to develop things and manage environments and cross program compatibility.
What would be interesting topics in Linux for you guys. I am in a Linux student club, have no experience with cyber security except the generic things, and we are looking to attract cyber security students since Linux doesn't have many students to maintain club status.
What distribution of emacs are you using? What setup for rust? Because the run/debug things work on mine.
Yeah, doing that in build.rs seems like a reasonable solution. Since we can't do that using proc macros.
I don't know if language server will keep giving me errors if the files are only linked through build.rs.
Thank you. Yeah, something like this would work for me as I can add in a script and run it before compiling. But it won't be a cross platform solution and windows/mac users are probably not going to be able to do anything. Maybe if I do the same thing but from build.rs it'll work. I'll try that.
That seems like a good compromise if I don't find something better. Thank you.
I'm hoping to make it easy for people to add more functions, that's why I want minimal code change required to add more functions.
Thank you for your detailed response.
I am ok using macros. But even proc macro only get the tokens and using in on the whole mod is unstable unless you use use it on mod sth{...}
instead of code being on in a different file (sth.rs).
The plug-in system is dynamic in a sense that my plans for it are loading them through shared libraries (.dll, .so) compiled separately by users. But I also have internally provided core plugins that come with the program. But rust ABI system is not that stable, so in worst case I might have to ask users to just add plugin code to some directory and re-compile program instead of loading from shared libraries. That's why I'm trying to make it as simple as possible. Asking users to modify the rust code somewhere else yo register the plugin might be met with resistance.
I was thinking that using build script to parse the source code and generating those codes could work, but that seemed hacky. So I was trying to see if there are better solutions, as it felt like a problem people might have come across themselves.
Hey this solution seems to work but it's not perfect; I don't know how we can improve it, and nothing to replace it with, but let's take it down asap.
He did not have to provide lifelong project and work on it. He just needed to donate his money and people in UN would have worked with that money. Even if it didn't work, he'd still have done a real great job by donating that much. And maybe we could have learn money is not the solution and we need to change approach.
Thank you. I just put the call with !
, I don't necessarily want a macro solution. Any solution is acceptable, my requirement is that I can just keep adding more mods with functions in src/functions/
and not have to register each function.
Inventory seems like the solution I am looking for. Although in my case, instead of collecting different values of the same type, I want to collect different types that all have same trait. But maybe I can make a temporary struct with Box<dyn _>
member to collect it if trying to collect it directly doesn't work. I do not plan to support WASM. I am planning to make C/C++ and Python API for the libraries though, so if it has problems with them, then I might have a problem.
How would the dog know, he's never been outside Utah.