Lines Matching refs:this
62 // Now, this is sort-of-tricky. MSDN documentation does not really make any claims as to safety of
100 /// Additionally, the callers of this function must also ensure that execution of the
110 /// Note that the behaviour of the `Library` loaded with this method is different from
111 /// Libraries loaded with [`os::unix::Library::this`]. For more information refer to [MSDN].
115 /// [`os::unix::Library::this`]: crate::os::unix::Library::this
117 pub fn this() -> Result<Library, crate::Error> {
154 // Make sure no winapi calls as a result of drop happen inside this closure, because
186 /// Additionally, the callers of this function must also ensure that execution of the
194 // Make sure no winapi calls as a result of drop happen inside this closure, because
219 /// Users of this API must specify the correct type of the function or variable loaded.
240 /// Users of this API must specify the correct type of the function or variable loaded.
277 /// You only need to call this if you are interested in handling any errors that may arise when
278 /// library is unloaded. Otherwise this will be done when `Library` is dropped.
291 // this time it would ignore the return result, which we already seen failing...
326 /// A major difference compared to the cross-platform `Symbol` is that this does not ensure that the
433 /// functions like [`Library::get`] with this DLL. Using this value causes writes to read-only
434 /// memory to raise an access violation. Use this flag when you want to load a DLL only to extract
452 /// Use this flag when you want to load a DLL only to extract messages or resources from it.
454 /// Unless the application depends on the file having the in-memory layout of an image, this value
512 /// If this value is used and `filename` specifies a relative path, the behaviour is undefined.
514 /// If this value is not used, or if `filename` does not specify a path, the system uses the