snafu | Easily assign underlying errors into domain-specific errors | Architecture library

I am writing a batch script that does a myriad of things. The one part I am stuck on is copying files/file structure from a location to my final image. The file structure looks something like this

I'm trying to use the snafu crate for error handling, but keep getting erros that my Error enum struct is missing the 'source' and that IntoError is not implimented for Error:

I'm building an app with rust. Using --cargo run --release successfully compiles the app and runs it, bringing up the GUI window for the app. However, when I manually open target/release/MyApp.exe, nothing happens. Checked when myapp.exe was last modifies shows that running --cargo run --release is updating the app.

I'm on windows 10 so I added "x86_64-pc-windows-msvc" as the build target.

I'm trying to use the Snafu crate for some basic error handling. In this case, I'm trying to return an Error when check_value() is given anything but a CustomInputValue::CiFloat. Based on what I was seeing in examples on this page from the docs, I thought this would work:

I have an error type that impls the Error trait, and it wraps an underlying error cause, so the source method returns Some(source). I want to know whether the Display impl on my error type should include a description of that source error, or not.

I can see two options:

1. Yes, include source in Display output, e.g. "Error opening database: No such file"

This makes it easy to print a whole error chain just by formatting with "{}" but impossible to only display the error itself without the underlying chain of source errors. Also it makes the source method a bit pointless and gives client code no choice on how to format separation between each error in the chain. Nevertheless this choice seems common enough in example code I have found.

1. No, just print the error itself e.g. "Error opening database" and leave it to client code to traverse and display source if it wants to include that in the output.

This gives client code the choice of whether to display just the surface error or the whole chain, and in the latter case how to format separation between each error in the chain. It leaves client code with the burden of iterating through the chain, and I haven't yet fallen upon a canonical utility for conveniently formatting an error chain from errors that each only Display themselves excluding source. (So of course I have my own.)

The snafu crate (which I really like) seems to hint at favoring option 2, in that an error variant with a source field but no display attribute defaults to formatting Display output that does not include source.

Maybe my real question here is: What is the purpose of the source method? Is it to make formatting error chains more flexible? Or should Display really output everything that should be user-visible about an error, and source is just there for developer-visible purposes?

I would love to see some definitive guidance on this, ideally in the documentation of the Error trait.

I was testing my regular expression skill at this site.
One of the questions was to come up with an expression that would match "fu, dofu, snafu" but not "futz, fusillade, functional, discombobulated".
I thought this an easy task and entered my answer as "fu$". To my surprise, the answer was not accepted. I then looked at the question more closely and found this phrase: "$ not allowed." Now, I'm stuck.

What should the regular expression be?

I've recently started learning Rust, and I'm currently trying to create a small API; I've made my own struct for an API Response and enum for an Error:

I'm trying to use Get-ChildItem in powershell (I'm using the ls alias) to return only files within a specific folder structure.

As an example, say I'm trying to list all files whose names end in .foobar.txt that reside within a folder called src, which in turn resides in a folder called even. I've tried using the command ls -r *\even\src\*.foobar.txt | % FullName. I thought the first wildcard * in the path would allow any path that ends in \even\src\ and that the second one would match only files that end in .foobar.txt. But it isn't returning all the files I expect. Here's the structure of the directory I'm testing it in:

I'm unable to actually access the member(s) in this undocumented class: BingMapsRESTToolkit.Response

Code in various places (e.g.)Bing Maps REST Services Toolkit - Access Value Outside of Delegate seem to copy the non-working example from MSDN.

For example, this method has no access to the array of Snapped coordinates contained in the Response object. The line where rez is assigned to the cast of the response gives us a null.