Fix incomplete links in documentation

[zimeg]

Summary

👋 Hello! This PR updates incomplete links in the documentation to point to the expected page.

Updated links

Here are the anchors to where these updates begin for each page:

• The Buffer page: https://docs.rs/ocl/latest/ocl/struct.Buffer.html#method.cmd
• The Context page: https://docs.rs/ocl/latest/ocl/struct.Context.html#method.builder
• The Image page: https://docs.rs/ocl/latest/ocl/struct.Image.html#method.cmd
• The ProQue page: https://docs.rs/ocl/latest/ocl/struct.ProQue.html#method.kernel_builder

Notes and questions

I'm slightly unsure of where the links in this section should lead, but am willing to make any suggested updates!

Formatting of the ocl::core::Status link is also troublesome and doesn't seem to want to appear inline... Would it make sense to add another line to reference these docs?

ocl/ocl/src/standard/device.rs

Lines 329 to 335 in d0f4b61

	/// Returns an `Err(ocl::core::Error::Status {...})` enum variant upon any
	/// OpenCL error. Calling [`.status()`] on the returned error will return
	/// an `Option(``[ocl::core::Status]``)` which can be unwrapped then
	/// matched to determine the precise reason for failure.
	///
	/// [`.status()`]: enum.Error.html#method.status
	/// [`ocl::core::Status`]: enum.Status.html

[c0gent]

Looks great.

Formatting of the ocl::core::Status link is also troublesome and doesn't seem to want to appear inline... Would it make sense to add another line to reference these docs?

Yes, that sounds good or whatever you think would be clearest.

I'm slightly unsure of where the links in this section should lead, but am willing to make any suggested updates!

Sorry which links?

[zimeg]

Thanks! Before making the inline link change, I wanted to share an answer and some findings for the following question:

Sorry which links?

For the ::list method, the links to .status() and ocl::core::Status are both pointing to missing links. I believe these resources might have moved in a refactoring of ocl_core.

Digging into the code, I think possible errors for ::list are of type ocl_core::functions::ApiError which implements .status()¹, but this method might not have link-able documentation. If this seems correct, I can add and link to this documentation?

And at a glance, it seems that the ocl::core::Status is now represented as ocl_core::Status. Replacing this link and related text (ocl::core::Error::Status) should be good, but I'm not fully sure...

Based on the implementation of .status(), I'm also wondering if the following change should be made, removing the Option around Status²:

  Calling `.status()` on the returned error will return an 
- `Option(ocl::core::Status)` which can be unwrapped then
+ `ocl_core::Status` which can be
  matched to determine the precise reason for failure.

Not meaning to turn these link updates into a code exploration, I'm just somewhat unfamiliar with the multi-crate structure 😅

Footnotes

1. ::list calls core::get_device_ids which sometimes returns an error from eval_errcode, which can be an ocl_core::functions::ApiError. ↩

2. I believe the Option<Status> is instead returned by .api_status() of ocl_core::error::Error ↩

[c0gent]

Ok great. It's been a while, I'll have to refamiliarize myself when I have time. I'll get back to you as soon as I can.

Appreciate your help!