ConcurrentQueue中的TryDequeue和TryTake有什么区别<>
根据可用的源代码，在TryTake调用TryDequeue时没有区别

/// <summary>
/// Attempts to remove and return an object from the <see cref="Concurrent.IProducerConsumerCollection{T}"/>.
/// </summary>
/// <param name="item">
/// When this method returns, if the operation was successful, <paramref name="item"/> contains the
/// object removed. If no object was available to be removed, the value is unspecified.
/// </param>
/// <returns>true if an element was removed and returned successfully; otherwise, false.</returns>
/// <remarks>For <see cref="ConcurrentQueue{T}"/>, this operation will attempt to remove the object
/// from the beginning of the <see cref="ConcurrentQueue{T}"/>.
/// </remarks>
bool IProducerConsumerCollection<T>.TryTake([MaybeNullWhen(false)] out T item) => TryDequeue(out item);

字符串
来源：https：//source.dot.net/#System.Private. CoreLib/ConcurrentQueue.cs，201
为什么要费心实现TryDequeue方法呢？
TryDequeue遵循与队列相关联的预期名称约定，并且是ConcurrentQueue<>本地的。同样，TryTake遵循通常与生产者/消费者模式相关联的命名约定。