Skip to main content

General questions and feedback on Microsoft's Quantum Developer Kit

.qs files

So, whoever is making these .qs sample files needs to use regular Intellisense rules for their comments so Intellisense works within the C# control code. Consider your first example, the TeleportationSample. IntelliSense has no idea what the TeleportClassicMessage type is on this line:

var received = TeleportClassicalMessage.Run(sim, sent).Result;

because in TeleportationSample.qs, the comments describing this operation do not follow the IntelliSense syntax of

/// <summary>
/// </summary>
/// <param name="args"></param>

and also because the .qs file type is unknown by Visual Studio, so your Visual Studio Extensibility solution needs to be modified to make that happen.

5 votes
Sign in Sign in with Microsoft - Quantum Computing
Signed in as (Sign out)

We’ll send you updates on this idea

Paula Scholz shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


Sign in Sign in with Microsoft - Quantum Computing
Signed in as (Sign out)
  • Mariano Gomez commented  ·   ·  Flag as inappropriate

    I also noticed that when running a Step Into (F11) on that same line, var received = TeleportClassicalMessage.Run(sim, sent).Result in the classical driver, it did not resolve to the definition of the TeleportClassicalMessage() operation. Is that by design or is this related to the intellisense issue? My assumption is, this is due to the compartmentalized roles of the driver and the quantum machine, but it's just an assumption. Can you confirm whether this is by design?

Feedback and Knowledge Base