There is an optional board param than may be passed in the constructor opts for all device classes. Simply put, it allows the user to specify which board they want to use in projects that have multiple boards. It is currently not documented anywhere and should probably be added to all the classes.

So many mistakes are made due to the default 'varying' decoration on a type when no decoration is given, that there should be a warning for it - disabled by default to not break current code.

#pragma warning(varying) //to enable
--wvarying // CLI to enable

The documentation should always be in sync with the latest changes. Currently, this involves me manually building it and pushing it into an S3 bucket. That could happen automatically through CI.

Additionally, it would be great if we could display a drop-down in the doc that allows viewing documentation for older versions of Zydis as well, similar to what docs.rs does for Rust

In Tutorial4 onwards, the render loop is destroying and recreating framebuffers every frame. Creation and destruction of objects in Vulkan are not lightweight operations - they are expected to have a sizeable runtime cost, and indeed do on some implementations.
This is documented in the Vulkan spec itself in fact, the second paragraph here: https://www.khronos.org/registry/vulkan/specs/1.0/html

Show difference quality as a numerical value between original (full size) image and upscaled image in the waif2x implementation comparison chart.

Probably using SSIM. Would be a informative comparison.

doc under Anakin/benchmark/README_CPU.md is out of data.
Three links of models points to 404 page
Those links in Anakin/benchmark/RNN/prepare.sh are also invalid.

As soon as both futures 0.2 and tokio 0.2 begin to stabilize, create an example which could potentially double as a tutorial and that uses some basic asynchronous features.

I am probably overlooking something super-obvious, so I hope this is only a quick question.

The config file says:

# Energy Versus Performance Preference Switch
# Usage: hwphint ${mode} ${algorithm} ${load_hint} ${normal_hint}
# Hints: see energy_performance_available_preferences

Where do I "see energy_performance_available_preferences"? Is there something similar for the algor

The vp instructions does not decode well.
For example:
"c5 f1 ef c9" should be decoded to "vpxor xmm1,xmm1,xmm1" (instead of "lds...").
"c5 f5 74 01" should be decoded to "vpcmpeqb ymm0,ymm1,ymmword ptr [ecx]" (instead of "lds...").

https://github.com/intel/llvm/blob/07a3616495afdac237f877a585c9a84d7838e95f/sycl/source/context.cpp#L43

Description of the corresponding constructor from the SYCL 1.2.1 spec:

Constructs a SYCL context instance using the SYCL device(s) in the deviceList parameter as the associated SYCL device(s) and the SYCL platform associated with each SYCL device in the deviceList parameter as the as

Add STIX/TAXII Client Functionality

Feature Request

I understand that Hippocampe can import data that is in plaintext formats. I think it would be great if a STIX/TAXII component was added.

See https://www.us-cert.gov/Information-Sharing-Specifications-Cybersecurity and https://oasis-open.github.io/cti-documentation/ for more information, and see https://github.com/eclecticiq/cabby f